Martin Langhoff wrote: > On 5/6/06, Junio C Hamano <junkio@cox.net> wrote: >>> Try doing >>> >>> git diff v1.3.0.. >>> >>> and think about what that actually _means_. Think about the fact that it >>> doesn't actually walk the commit chain at all: it diffs the trees >>> between v1.3.0 and the current one. What if the rename happened in a >>> commit in the middle? >> >> Then the automated renames detection will miss it given that the other >> accumulated differences are large enough, and the suggested workarounds >> _are_ precisely walking the commit chain. > > I agree here with Pasky that after a while the automated > renames/copy/splitup detection will miss the operation in cases where > it would be interesting to note it to the user. Perhaps an option to do rename detection with walking the commit chain? -- Jakub Narebski Warsaw, Poland - 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 Sat May 06 17:34:27 2006
This archive was generated by hypermail 2.1.8 : 2006-05-06 17:34:49 EST