On 11/17/06, Petr Baudis <pasky@suse.cz> wrote: > * cg-log does not follow history across renames anymore; it never really > actually worked and was instead causing problems and random error > messages. There needs to be git-core support for this funcionality, > hacking it with a perl filter is bad design, so I'm not going to fix > the filter (but I'd take patches if someone else did ;). I was looking at the follow renames Perl script last week (hey, I was bored!) and while I could tell it didn't work, I did get the feeling that it wasn't an impossible task, at least for the 'explicit paths' case. For the 'whole tree' and subpath cases it _is_ tricky, and would be faster to solve within git, but not impossible. And even then, I am tempted to think that git log could provide some better hints than it does today when walking the whole tree or subpaths, so that cg-log or gitk can ask [if relevant] for selective rename info. I am curious as to why you see it as bad design... cheers, martin - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Fri Nov 17 12:45:14 2006
This archive was generated by hypermail 2.1.8 : 2006-11-17 12:48:10 EST