| commit | 6de9433fd0525632094f3cc172a606f217fa2097 | |
| author | Jakub Narebski <jnareb@gmail.com> | |
| Fri, 24 Jul 2009 22:44:02 +0000 (25 00:44 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sat, 25 Jul 2009 08:39:16 +0000 (25 01:39 -0700) | ||
| tree | d7c2c71f27945775d430073f8fcc885f3b35c45d | treesnapshot (tar.gz zip) |
| parent | 0a49a7997b7380c1552786adb544d50d005368f8 | 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 first cell in row, 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 slightly 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 first cell in row, 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 slightly 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 |