From: Paolo Bonzini <bonzini@gnu.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Mike Galbraith <efault@gmx.de>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: git remote update -> rejected
Date: Tue, 22 Apr 2008 18:23:36 +0200 [thread overview]
Message-ID: <480E1108.5090701@gnu.org> (raw)
In-Reply-To: <480E03A9.3040401@gnu.org>
>>> What about changing --mirror to add a push line instead of a fetch line?
>>
>> I would not expect --mirror to add a push line when "git-remote add"
>> without --mirror does not a push line either.
>
> Let me reverse the question. When does it make sense to use "git-remote
> add --mirror" with the current implementation?
>
> It's not a rhetoric question. I know when it would make sense to have
> push refspecs on a remote for which you plan to use "git push --mirror"
> (and in "next", that is the case if you create the remote with
> "git-remote add --mirror"). But I'm a total newbie for things that do
> not fit my workflows, so I don't know when it would make sense to pull
> from that kind of remote.
And actually, I just realized that what I expected from --mirror is this:
[remote "mirror"]
url = blah
fetch = +refs/heads/*:refs/remotes/mirror/*
push = +refs/heads/*:refs/heads/*
mirror
... so that I can check the state of the mirror with "git log -1
mirror/master", and still the push refspec is there so that my local
remotes are not entirely mirrored.
Paolo
next prev parent reply other threads:[~2008-04-22 16:24 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
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 [this message]
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=480E1108.5090701@gnu.org \
--to=bonzini@gnu.org \
--cc=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 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.