Robert Zeh <robert.allan.zeh@xxxxxxxxx> wrote: > On Feb 17, 2010, at 5:23 PM, Eric Wong <normalperson@xxxxxxxx> wrote: >> There was a rather large amount of changes between 1.6.5.2 so some >> regressions could've slipped in. A bisection would definitely help >> us track down the cause. > > I will attempt a bisection Thursday. Awesome, thanks. >> Does the repository you're using svn:mergeinfo use by any chance? > > The repository does use mergeinfo, but much later in the revision > history then when the problem shows up. > > Do you have any advice on how to write a test for this behaviour, since > the problem is not apparent from looking at the repo? I do not like the > idea of a test looking at a log but that is all I can think of right now. Andrew and Sam are the people to ask about mergeinfo, but I've found reading logs valuable for tracking down many issues in the past. I'm not 100% convinced mergeinfo itself is the problem (but it's the code I'm least familiar with), and there were also some changes with globbing (which I believe were harmless improvements). -- Eric Wong -- 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