Petr Baudis <pasky@xxxxxxx> writes: > On Mon, Aug 27, 2007 at 10:51:04AM CEST, Johannes Schindelin wrote: >> On Sun, 26 Aug 2007, Petr Baudis wrote: >> ... >> You were too busy playing Go, probably, so you missed my patch which tried >> to fix this issue. Alas, it broke more than it fixed, so it was just >> worked around for git-clone --bare. > > AFAICS that patch is already applied as well; I tried to ask on IRC > for more fixes but seemed there is none and Junio almost threatened to > even release 1.5.3 with this bug. ;-) Well, I just needed something that > would fix this on repo.or.cz which totally broke after upgrade to new > Git version. Heh, "threaten" is a good word. Could you two help me with this issue? I suspect you (and probably Shawn) have the most "old fashioned" scripts that rather rely on pre-work-tree behaviour and have better chance than others to catch unintended side effects like the current "git --bare init" issues. - 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
