Re: That improved git-gui blame viewer..

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 12, 2007, 06:52 UTC
Message-ID: <7vbqflll55.fsf@assigned-by-dhcp.pobox.com>
In-Reply-To: <e5bfff550706112316j42c7c8e8uf8383de990ca9707@mail.gmail.com>

"Marco Costalba" <mcostalba@gmail.com> writes:

Show 7 quoted lines

> On 6/11/07, Junio C Hamano <gitster@pobox.com> wrote:
>>
>> An option to re-blame starting from the parent commit of what is
>> currently blamed (i.e. "peel" one level) would certainly be
>> interesting but I do not think git-gui has it (yet).
>
> Not to advertise, but qgit has already that from ages.

Advertising is good.

> Annotate algorithm of qgit is little different in that it starts from
> the oldest revision that modified a file and goes to the latest. In
> this way we can have the whole file history annotated in one pass and
> very fast.

I am not sure about two things in this description.

 (1) Are you emulating CVS-like "a file has an identity, and we
     follow its changes" model?  How does it handle file split,
     merge, and code movement in general?

 (2) It is unclear why going from old to new has the advantage
     of being "one pass", implication of which is that the
     opposite direction needs to be done as more than one pass.
     Care to enlighten?