From: Junio C Hamano <gitster@pobox.com>
To: Nico -telmich- Schottelius <nico-linux-git@schottelius.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Steffen Prohaska <prohaska@zib.de>,
git@vger.kernel.org
Subject: Re: Adding push configuration to .git/config
Date: Thu, 29 Nov 2007 14:46:33 -0800 [thread overview]
Message-ID: <7v1wa8vfee.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20071128221559.GC22395@denkbrett.schottelius.org> (nico-linux-git@schottelius.org's message of "Wed, 28 Nov 2007 23:15:59 +0100")
Nico -telmich- Schottelius <nico-linux-git@schottelius.org> writes:
> ...
> [branch "otherbranch"]
> merge = otherremote
> push = otherremote
> push = classmate
> push = myremote
> --------------------------------------------------------------------------------
>
> What do you think about that approach?
Huh?
Is this a reinjection of an ancient message by some gateway?
You were already told branch.$name.merge has a defined meaning and
syntax, and you cannot make it refer to a remote shorthand without
breaking an existing setup.
Also if you want to have more than one destination repository for a
single push, I think that is already supported with remote.$name.url.
IIRC, there was a suggestion to enhance remote.$name configuration in
this way instead, so that you can use different URL for fetching and
pushing:
[branch "foo"]
remote = "there"
merge = refs/heads/master
[remote "there"]
url = git://git.there.xz/repo.git
push_url = git.there.xz:repo.git
push_url = git.there.xz:backup.git
fetch = refs/heads/*:refs/remotes/there/*
I further vaguely recall that the comments on the alternative were
positive (it might have been you who responded, or somebody else, I do
not remember).
next prev parent reply other threads:[~2007-11-29 22:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 10:55 Adding push configuration to .git/config Nico -telmich- Schottelius
2007-11-21 22:02 ` Steffen Prohaska
2007-11-22 1:48 ` Junio C Hamano
2007-11-22 7:08 ` Steffen Prohaska
2007-11-22 7:52 ` Andreas Ericsson
2007-11-22 8:28 ` Junio C Hamano
2007-11-22 8:23 ` Junio C Hamano
2007-11-22 8:54 ` Steffen Prohaska
2007-11-22 11:23 ` Johannes Schindelin
2007-11-22 11:49 ` Junio C Hamano
2007-11-22 11:59 ` Andreas Ericsson
2007-11-22 18:22 ` Steffen Prohaska
2007-11-28 22:15 ` Nico -telmich- Schottelius
2007-11-28 23:50 ` Johannes Schindelin
2007-11-29 22:46 ` Junio C Hamano [this message]
2007-11-30 0:37 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2007-11-23 13:07 MichaelTiloDressel
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=7v1wa8vfee.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=nico-linux-git@schottelius.org \
--cc=prohaska@zib.de \
/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).