On Thu, Nov 18, 2010 at 4:52 PM, Matthijs Kooijman <matthijs@xxxxxxxx> wrote: > Hi all, > >> I've been using git for exactly this purpose succesfully for a while now >> (git 1.5.6.5 from Debian stable and I think also 1.7.2.3 from Debian >> testing). > Coming back to the testing machine I was using this on, I see this > problem as well now. I'm pretty sure it wasn't there before, which would > mean it was introduced by a recent upgrade. > > Checking the logs shows that I was running 1.7.1 before, and now 1.7.2.3 > is broken. Downgrading to 1.7.1 indeed removes the problem. > > I've rummaged around in the source a bit, haven't found the cause yet > (and I'm out of time now). Alternatively, you could try to bisect, with "git bisect", between these two commits, 1.7.2.3=bad and 1.7.1=good. It is roughly 10 steps. HTH, Santi -- 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