Re: recent change in git.git/master broke my repos

From: Jeff King <peff@peff.net>
Date: Oct 25, 2007, 16:56 UTC
Message-ID: <20071025165633.GA24143@coredump.intra.peff.net>
In-Reply-To: <86oden6z97.fsf@blue.stonehenge.com>

On Thu, Oct 25, 2007 at 07:32:36AM -0700, Randal L. Schwartz wrote:

Show 15 quoted lines

> I have echo "ref: refs/remotes/origin/master" >.git/refs/heads/upstream
> so that my daily update script can go:
> 
>    git-fetch
>    if [ repo is on master, and is not dirty ];
>       git-merge upstream
>    fi
> 
> Yesterday that worked.
> 
> Today I get a rash of:
> 
>   fatal: Couldn't find remote ref refs/remotes/origin/master
> 
> from my git-fetch.

Randal and I discussed this a bit on IRC, and it turns out not to be related to the 'upstream' symref. Instead, he had a broken branch.master.merge config that pointed to "refs/remotes/origin/master" (which you can see from his script above doesn't actually get used).

So presumably the old git-fetch didn't care that the contents of branch.*.master didn't exist (it's just that nothing got marked for merging), but the one just merged from the db/fetch-pack topic does.

Is this behavior change intentional?

-Peff