From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: Mike Galbraith <efault@gmx.de>,
Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: git remote update -> rejected
Date: Tue, 22 Apr 2008 12:58:07 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0804221250010.4460@eeepc-johanness> (raw)
In-Reply-To: <20080422111113.GB11238@sigill.intra.peff.net>
Hi Peff,
On Tue, 22 Apr 2008, Jeff King wrote:
> 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
next prev parent reply other threads:[~2008-04-22 11:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 9:48 git remote update -> rejected Mike Galbraith
2008-04-22 10:34 ` Jeff King
2008-04-22 10:55 ` Mike Galbraith
2008-04-22 11:11 ` Jeff King
2008-04-22 11:58 ` Johannes Schindelin [this message]
2008-04-22 12:56 ` Jeff King
2008-04-22 13:03 ` Johannes Schindelin
2008-04-22 13:09 ` Jeff King
2008-04-22 13:26 ` [PATCH] builtin-remote: resurrect forced updates to tracked branches Johannes Schindelin
2008-04-22 17:00 ` git remote update -> rejected Junio C Hamano
2008-04-22 12:41 ` Teemu Likonen
2008-04-22 12:56 ` Johannes Schindelin
2008-04-22 13:01 ` Jeff King
2008-04-22 13:05 ` Johannes Schindelin
2008-04-22 13:53 ` Paolo Bonzini
2008-04-22 13:39 ` Teemu Likonen
2008-04-22 13:49 ` Johannes Schindelin
2008-04-22 14:04 ` Teemu Likonen
2008-04-22 14:10 ` Paolo Bonzini
2008-04-22 15:08 ` Johannes Schindelin
2008-04-22 15:26 ` Paolo Bonzini
2008-04-22 16:23 ` Paolo Bonzini
2008-04-22 16:42 ` Johannes Schindelin
2008-04-22 16:50 ` Junio C Hamano
2008-04-22 17:23 ` [PATCH] remote add: disallow --master and --mirror with non-bare repositories Johannes Schindelin
2008-04-22 18:45 ` Paolo Bonzini
2008-04-22 18:46 ` [PATCH] remote add: disallow --master and --mirror with non-bare repositories (review) Paolo Bonzini
2008-04-22 22:04 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.00.0804221250010.4460@eeepc-johanness \
--to=johannes.schindelin@gmx.de \
--cc=efault@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox