From: Junio C Hamano <gitster@pobox.com>
Date: Sat, 25 Jul 2009 00:39:27 GMT
Subject: Re: [PATCH 02/10] gitweb: Mark boundary commits in 'blame' view
Message-ID: <7vskgl38ao.fsf@alter.siamese.dyndns.org>
In-Reply-To: <200907250232.28561.jnareb@gmail.com>

Jakub Narebski <jnareb@gmail.com> writes:

> On Sat, 25 July 2009, Junio C Hamano wrote:
>> Jakub Narebski <jnareb@gmail.com> writes:
>> 
>> > 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.
>
> Well, currently 'blame' view in gitweb doesn't allow to limit revision
> range from below, i.e. to state "low" commit; it doesn't use 'hpb' 
> (hash_parent_base) parameter.  So boundary commit means root commit.

Yes, but I think it is the same thing.  The initial import of a tarball,
that is "a distant stable past as opposed to more recent breakages".