Re: [PATCH 02/10] gitweb: Mark boundary commits in 'blame' view
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:47:06
Jakub Narebski [off-list ref] writes:
quoted hunk
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). ...diff --git a/gitweb/gitweb.css b/gitweb/gitweb.css index 70b7c2f..f47709b 100644 --- a/gitweb/gitweb.css +++ b/gitweb/gitweb.css@@ -242,6 +242,10 @@ tr.dark:hover { background-color: #edece6; } +tr.boundary td.sha1 { + font-weight: bold; +} +
"boundary" means that "blame low..hight file" attributed the line to the "low" commit, not because the commit introduced the line, but because the user said not to bother digging further. I had an assumption that in such a bounded blame, lines attributed to the boundary commit are not very interesting (they belong to a distant stable past that the user does not care much about, as opposed to more recent breakages), and that is exactly the same reasoning behind the -b option of "git blame" command. I would have expected the boundary to be shown in weaker decoration (e.g. gray letters as opposed to black), not in stronger annotation. Perhaps you are talking about something different? I am a bit puzzled.