Re: [BUG?] push to mirrior interferes with parallel operations

From: Jeff King <peff@peff.net>
Date: Nov 18, 2010, 17:58 UTC
Message-ID: <20101118175810.GB26505@sigill.intra.peff.net>
In-Reply-To: <20101118175007.GA26505@sigill.intra.peff.net>

On Thu, Nov 18, 2010 at 12:50:08PM -0500, Jeff King wrote:

Show 8 quoted lines

> >     [remote "backup"]
> > 	url = /mnt/server/path/to/repo.git
> > 	fetch = +refs/*:refs/*
> > 	mirror = true
> 
> I think we don't want to be doing the opportunistic update in this case.
> But what is the correct rule for deciding not to do it? I can think of a
> few possibilities:

Thinking on this more, perhaps it really is the fetch refspec there that is the problem (as you initially suggested).

It seems to me there are really two kinds of mirrors: one where you will fetch everything from the remote, and one where you will push everything to the remote.

You have the latter kind, and the fetch refspec is just causing problems. Removing it would solve not only this issue, but also the fact that you would never want to run "git fetch backup", even accidentally, in your repo, as it would overwrite your local work.

So I think we need --mirror=push, or something similar.

-Peff