Junio C Hamano wrote: > Jonathan Nieder <jrnieder@xxxxxxxxx> writes: >> This server-side deadlock started being triggered by shallow clones >> when sv.gnu.org upgraded to v1.7.2.5 a couple of months ago[1]. So it >> might be worth thinking about how to help upgrade-averse server admins >> to fix it. > > Upgrade-averse people can be fixed by keeping them closer to the tip, no? > I don't plan to issue any more maintenance release on 1.7.2.X track beyond > what is already released, unless there is a high priority security fix or > something. > > Placing it on 1.7.4.X and newer maintenance tracks is a separate matter. Ok, that's fine with me. (To be clear, I was suggesting cherry-picking to the branches but not making a release, though I realize that would mean more time wasted the next time it is time to make a high priority security fix.) I'll cherry-pick it as a Debian-specific patch, which should be good enough to get shallow clones working again on the affected servers. -- 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