git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Jeff King <peff@peff.net>, Jan Hudec <bulb@ucw.cz>, git@vger.kernel.org
Subject: Re: [BUG?] push to mirrior interferes with parallel operations
Date: Fri, 19 Nov 2010 15:32:56 -0600	[thread overview]
Message-ID: <20101119213256.GA579@burratino> (raw)
In-Reply-To: <m2ipzt14rh.fsf@igel.home>

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.

Jeff seems to have meant

	When in a non-bare repo, it only makes sense to push.

which is to say, push --mirror makes sense from a bare repo but fetch
--mirror does not.  However, I think you read

	When pushing, it only makes sense to use a non-bare repo

to which a reasonable response is to point out that no, push --mirror
makes sense from a bare repo after all.

I see no disagreement here. :)

  parent reply	other threads:[~2010-11-19 21:33 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
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 [this message]
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=20101119213256.GA579@burratino \
    --to=jrnieder@gmail.com \
    --cc=bulb@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --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).