Stephen Bannasch <stephen.bannasch@xxxxxxxxxxxxx> wrote: > At 7:30 PM -0800 1/27/09, Shawn O. Pearce wrote: >> PJ - the short story here is, to forever work around these buggy >> 1.6.1 clients, you'd have to either run an old server forever, >> or forever run a patched server that disables the newer ".have" >> extension in the advertised data written by git-upload-pack. >> There just isn't a way to hide this from the client. >> >> Really though, I'd recommend getting your users to upgrade to a >> non-buggy client. Pasky has the same problem on repo.or.cz; if >> he doesn't have it already he will soon when he upgrades... > > Do you know if this problem is fixed in tag v1.6.1.1? > > Tagger: Junio C Hamano <gitster@xxxxxxxxx> > Date: Sun Jan 25 12:41:48 2009 -0800 > commit 5c415311f743ccb11a50f350ff1c385778f049d6 Without even checking Git I can tell you it isn't fixed by 1.6.1.1. The date on the tag is Jan 25th, 2 full days before PJ reported the problem and a solution was proposed... -- Shawn. -- 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
