We are using git 1.4.4.1, the latest I thought available, not 1.4.4.4 (perhaps you mis-typed?). In any case, I personally would love to try the latest build of git, but I don't think I can convince the rest of the company to do so. I just got an email from one of the developers. He seems to think this is alleviated by using bash instead of tcsh. He said he is debugging his environment to see if he can isolate the problem. I have asked for more details and if I can find out more, I will certainly communicate it here. If I were to get people to agree to try the latest git build, would I be able to just let the developer install and use it on his machine, or would I need to also update our company repo? If the former, I would have a much easier time convincing them. Thanks. Bill On Saturday, January 20, 2007 at 11:33:38 (-0800) Junio C Hamano writes: >Junio C Hamano <junkio@xxxxxxx> writes: > >> Bill Lear <rael@xxxxxxxxxx> writes: >> >>> % git push >>> updating 'refs/heads/master' >>> from 6b421066e842203e383e1dc466c1cdef10de56b1 >>> to 2a8e554ae0c99d44988690c9fce693b3f5f128fa >>> Generating pack... >>> Done counting 61 objects. >>> Result has 32 objects. >>> Deltifying 32 objects. >>> 100% (32/32) done >>> Writing 32 objects. >>> 100% (32/32) done >>> Total 32, written 32 (delta 18), reused 0 (delta 0) >>> Unpacking 32 objects >>> fatal: protocol error: bad line length character > >By the way, I can see from the pack-objects output above that >you seem to be using git before commit 67c08ce1 (Nov 29, 2006); >most likely you are using the official 1.4.4.4? > >Is it possible for you to try git built from the tip of 'master' >to see if it reproduces? - 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