Re: Finally implement "git log --follow"

From: Marco Costalba <mcostalba@gmail.com>
Date: Jun 20, 2007, 06:27 UTC
Message-ID: <e5bfff550706192327l187b30eblb5bd5e4e76b3eab6@mail.gmail.com>
In-Reply-To: <alpine.LFD.0.98.0706191358180.3593@woody.linux-foundation.org>

On 6/19/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:

Show 9 quoted lines

>
> Ok, I've really held off doing this too damn long, because I'm lazy, and I
> was always hoping that somebody else would do it.
>
> But no, people keep asking for it, but nobody actually did anything, so I
> decided I might as well bite the bullet, and instead of telling people
> they could add a "--follow" flag to "git log" to do what they want to do,
> I decided that it looks like I just have to do it for them..
>

Thanks,

  now I have one more reason to switch from using git-rev-list to
git-log in qgit, file history annotation, that is currently based on
git-rev-list, will automatically gain a powerful feature.

Marco

P.S: The only thing that is still missing in git-log against git-rev-list is a --stdin option. This is needed because with 40 chars SHA the command line could became very long in case of repos with many tags/branches or when loading StGIT unapplied patches (one sha per patch) and one git-rev-list call to loading them all.

Without --stdin we break easily on _some_ OS and in the worst cases (a lot of unapplied patches) *even* under Linux.