Hi, On Thu, May 21, 2009 at 10:29 PM, Tony Finch <dot@xxxxxxxx> wrote: > ...Git's error message is misleading: the problem is > nothing to do with running git update-server-info (see below). you're right. Perhaps git should check if the repo (on http://) exists first, before printing that message. > Its > behaviour is inconsistent: git retries after appending .git if you are > fetching from a local repository or ssh:// or git:// URLs but not for > http:// URLs. that's true too. > Actually maybe there's a third bug: it says it has initialized > a repository but it removes it again if the clone fails. well, if the clone fails, then the cloned repo would be in an incomplete state, so removing it isn't that bad an idea. Perhaps an option could be made to prevents clone from doing this, so that one could try restarting the clone. -- Cheers, Ray Chuan -- 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