Defect #11040

Git commit messages have strange formatting:

Added by Øystein Walle over 10 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:SCM
Target version:-
Resolution: Affected version:1.4.2

Description

In both the overview of a repository and in the details of a specific commit "ascii-style" lists are shown in a strange manner. Note in the attached images that item no. 2 onwards have an extra space of padding on the left. Additionally, the whole list (including the first item) get a monospaced font.

Server: Ubuntu 12.04 server
Git: 1.7.9.5

The output of 'git log' in the actual repo on the server is:

Improved daemon functionality

New features to the daemon:

 - It will check if it is already running via a lockfile
 - It handles SIGTERM: writes to the log and deletes the lockfile
 - blah blah blah
 - The usage() text reflects the changes

with one space before and after the dashes. The missing linebreak (subjective) is covered in Issue #10968. Also related is Issue #10886.

It seems the space before the first item in the list starts "monospace mode" and is therefore stripped.

view-revision.png - How the commit messages looks on the page of that specific commit (5.55 KB) Øystein Walle, 2012-05-29 11:12

overview.png - How the commit messages looks in the repository overview (7.97 KB) Øystein Walle, 2012-05-29 11:12


Related issues

Duplicated by Redmine - Feature #15160: commit log Closed
Duplicated by Redmine - Defect #15204: Git commit message not formatted at all in <project>/repo... Closed

History

#1 Updated by Toshi MARUYAMA almost 9 years ago

#2 Updated by Toshi MARUYAMA almost 9 years ago

  • Duplicated by Defect #15204: Git commit message not formatted at all in <project>/repository/revisions/<SHA> view added

Also available in: Atom PDF