Hi, On Sun, 13 Jul 2008, Sverre Rabbelier wrote: > On Sun, Jul 13, 2008 at 3:24 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > > <explanation of the git log traversal machinery snipped> > > > In order to follow renames reliably in a merge heavy history, you need to > > keep track of the pathname the file you are interested in appears as _in > > each commit_. As you traverse down the history, you pass down the > > pathname to the parent you visit, so while you are traversing from 'x' to > > earlier 'x', you will keep following "git-gui/git-gui.sh", while you > > traverse down to 'o', you will inspect "git-gui.sh". > > > > The data structure the revision traversal machinery uses does not support > > this "path-per-commit" natively. > > Would it be possible to go for a slightly less complicated approach > and instead of passing replacing the tracked file, append it? Maybe I miss something, but do you not have to keep track of the file names, in order to keep track of the proper statistics? If that is the case, appending does not cut it. Ciao, Dscho -- To unsubscribe from this list: 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
