From: Jan Hudec <bulb@ucw.cz>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Does it make sense to pull from mirror? (Re: [BUG?] push to mirrior interferes with parallel operations)
Date: Thu, 18 Nov 2010 19:49:04 +0100 [thread overview]
Message-ID: <20101118184904.GO3693@efreet.light.src> (raw)
In-Reply-To: <20101118175810.GB26505@sigill.intra.peff.net>
On Thu, Nov 18, 2010 at 12:58:11 -0500, Jeff King wrote:
> 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.
Accidentally did it already. Fortunately it just died with something like
"refusing to pull to checked out branch of non-bare repository"
and did nothing at all.
> So I think we need --mirror=push, or something similar.
Does it *ever* make sense to have a non-bare pull mirror. I think it does
not.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
next prev parent reply other threads:[~2010-11-18 18:49 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 ` Jan Hudec [this message]
2010-11-18 19:05 ` Does it make sense to pull from mirror? (Re: [BUG?] push to mirrior interferes with parallel operations) 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
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=20101118184904.GO3693@efreet.light.src \
--to=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.