Re: [PATCH] git-blame: Use the same tests for git-blame as for git-annotate
- From
Martin Langhoff <martin.langhoff@gmail.com>
- Date
- Mar 6, 2006, 00:29 UTC
- Message-ID
- <46a038f90603051629ke34a0a6u89dad995bbd777b0@mail.gmail.com>
- In-Reply-To
- <440B751F.5000801@michonline.com>
On 3/6/06, Ryan Anderson <ryan@michonline.com> wrote:
> Along these lines, if anyone can pin down the complicated cases that > annotate and blame get differently, adding them as a test would be > *exceedingly* appreciated, even if it makes annotate (or blame) fail for > a bit, it gives us something to work against.
It would be great if they both worked properly with paths that existed in the past. Right now, I can't git-annotate or git-blame a file I know was there in a past revision. I think I had taught Johannes' annotate to deal with this, or at least intended to. As things stand, git-annotate/git-blame need a checkout, which is really silly.
Tools like gitweb and cvsserver should be able to do:
GIT_DIR=/somebarerepo/git.git git-(annotate|blame) -h headname Makefile
and not worry about creating a temporary index *and* checking out Makefile so that things work. That's what cvsserver does now, anyway. Ugly :-(
cheers,
m