> So this bug was _literally_ introduced three days ago, and it was > introduced by a set of patches that tried to _avoid_ the problem. > > Sad. The old code was perfectly good. The new code was unsafe, but thought > it was better. See commit 93822c2239a336e5cb583549071c59202ef6c5b2 for > details. Weird. I think the system where the tree got corrupted had git 1.4.4.4. -- MST - 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