| commit | a6be48b958bdc34bf36112e501613062b3d1a79f | |
| author | Jakub Narebski <jnareb@gmail.com> | |
| Fri, 10 Jul 2009 21:55:44 +0000 (10 23:55 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 13 Jul 2009 18:11:20 +0000 (13 11:11 -0700) | ||
| tree | 6905abdcb25dda77b8f2513a6c146aa441818bd6 | treesnapshot (tar.gz zip) |
| parent | d9eb0205a217984f3e70bf18ae66c02a22d3d475 | commitdiff |
gitweb: Mark boundary commits in 'blame' view
Use "boundary" class to mark boundary commits, which currently results
in using bold weight font for SHA-1 of a commit (to be more exact for
all text in the cell that contains SHA-1 of a commit).
Detecting boundary commits is done by watching for "boundary" header
in "git blame -p" output. Because this header doesn't carry
additional data the regular expression for blame header fields had to
be adjusted.
With current gitweb API only root (parentless) commits can be boundary
commits.
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Use "boundary" class to mark boundary commits, which currently results
in using bold weight font for SHA-1 of a commit (to be more exact for
all text in the cell that contains SHA-1 of a commit).
Detecting boundary commits is done by watching for "boundary" header
in "git blame -p" output. Because this header doesn't carry
additional data the regular expression for blame header fields had to
be adjusted.
With current gitweb API only root (parentless) commits can be boundary
commits.
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| gitweb/gitweb.css | diffblobblamehistory | |
| gitweb/gitweb.perl | diffblobblamehistory |