From: Jeff King <peff@peff.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Jan Hudec <bulb@ucw.cz>, git@vger.kernel.org
Subject: Re: [BUG?] push to mirrior interferes with parallel operations
Date: Fri, 19 Nov 2010 14:46:28 -0500 [thread overview]
Message-ID: <20101119194628.GA15466@sigill.intra.peff.net> (raw)
In-Reply-To: <m2ipzt14rh.fsf@igel.home>
On Fri, Nov 19, 2010 at 08:40:18PM +0100, Andreas Schwab wrote:
> Jeff King <peff@peff.net> writes:
>
> > it really only makes sense to push from a non-bare repo,
>
> Why? The repo could itself be a mirror.
Why do you have a working directory if you are going to have a refspec
that overwrites HEAD behind your back (which, IIRC, git will simply barf
on, so all of your fetches will fail)?
Yes, you could do something complex like have a mirror that lives on a
detached HEAD and automagically updates the working tree based on some
particular ref. But at that point I think you are going to be setting up
.git/config manually, anyway. This is really about what default git "git
remote add --mirror" should set up.
-Peff
next prev parent reply other threads:[~2010-11-19 19:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 7:39 [BUG?] push to mirrior interferes with parallel operations Jan Hudec
2010-11-18 17:50 ` Jeff King
2010-11-18 17:58 ` Jeff King
2010-11-18 18:49 ` Does it make sense to pull from mirror? (Re: [BUG?] push to mirrior interferes with parallel operations) Jan Hudec
2010-11-18 19:05 ` Jeff King
2010-11-18 18:42 ` [BUG?] push to mirrior interferes with parallel operations Jan Hudec
2010-11-18 19:04 ` Jeff King
2010-11-19 19:40 ` Andreas Schwab
2010-11-19 19:46 ` Jeff King [this message]
2010-11-19 21:18 ` Andreas Schwab
2010-11-19 21:21 ` Jeff King
2010-11-19 21:29 ` Andreas Schwab
2010-11-19 21:51 ` Jeff King
2010-11-19 21:32 ` Jonathan Nieder
2010-11-19 21:54 ` Jeff King
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=20101119194628.GA15466@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=schwab@linux-m68k.org \
/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;
as well as URLs for NNTP newsgroup(s).