On Sun, Sep 13, 2009 at 01:57:37PM -0700, Junio C Hamano wrote: > > 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/next > > I think saying "does not exist" will repeat the same mistake of > overguessing you are trying to rectify. You are right, of course. I think your wording makes sense, then (otherwise we get stuck with "well, we didn't fetch it. Maybe because it didn't exist. Or maybe because your configuration didn't include it."). -Peff -- 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