On Friday 2006 December 15 00:02, Junio C Hamano wrote: > Andy, which version of git do you run (I presume they are the > same version, as you are doing the local fetching), and which > version of git was the "slightly out of date" repository > prepared with? One of them is switched off and in another place at the moment, so this is from memory: The initial repository was made with origin/master from a few days ago, that's the one I've been calling "out-of-date". I cloned that to another computer and continued adding patches using "1.4.4.1.g3ece-dirty" (the dirt is just my colour branch patch on top of ba988a83). The fetch is being done back on the original system which has the newer git but older repository. I hadn't realised it was quite a serious as these responses are making it sound. I'll gather more precise data upon my return home. On the up-to-date computer I've just made a fresh repository, set .git/config to point locally at the full repository and ran git-fetch. Interestingly, that has worked perfectly. Clearly it is version-specific. I'll do a bit of bisection later and see if I can nail the problem down. Andy -- Dr Andy Parkins, M Eng (hons), MIEE andyparkins@xxxxxxxxx - 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