Re: git remote update -> rejected

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Apr 22, 2008, 11:58 UTC
Message-ID: <alpine.DEB.1.00.0804221250010.4460@eeepc-johanness>
In-Reply-To: <20080422111113.GB11238@sigill.intra.peff.net>

Hi Peff,

On Tue, 22 Apr 2008, Jeff King wrote:

Show 14 quoted lines

> On Tue, Apr 22, 2008 at 12:55:03PM +0200, Mike Galbraith wrote:
> 
> > >   [remote "x86"]
> > >     url = ...
> > >     fetch = +refs/heads/*:refs/remotes/x86/*
> > > 
> > > See 'git help fetch' for details.
> > 
> > Thanks a bunch.  I'll try it.  I notice that origin and linux-next
> > already had + prefix.  Presumably that came from the home repo.
> 
> Cloning creates an origin with '+' in the fetch line, but "git remote
> add" doesn't seem to. Hrm, it looks like this is a regression from the
> recent rewrite in C.

Thanks for working on this: I missed this thread (had too many mails to catch up with).

> Dscho, is this a bug, or was there a conscious decision that I missed?

It was a concious decision, but maybe it was wrong.

My rationale was this: if I mirror another person's repository, I want all the history. And I do want to keep it, even if the other person decides to clean the original repository out.

(In this case, the reflogs would not help, since I do not have a HEAD reflog for all the deleted branches, and deleting the refs deletes their reflogs, too.)

But as I said, my rationale may very well be wrong.

Ciao, Dscho