On 3/6/06, Ryan Anderson <ryan@xxxxxxxxxxxxxx> 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 - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html