Re: Confusing git pull error message
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 13, 2009, 20:57 UTC
- Message-ID
- <7vfxaqpnpa.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <20090913204231.GA8654@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> What you have here is precisely what we observed. But I think one of the > complaints was to say more explicitly "that ref doesn't exist on the > remote", which I think should be the case if we have got to this point > (anything else would have triggered an error in fetch).
Wouldn't you get into the situation with this?
[remote "origin"]
fetch = refs/heads/master:refs/heads/master
[branch "master"]
remote = origin
merge = refs/heads/nextI think saying "does not exist" will repeat the same mistake of overguessing you are trying to rectify.