From: Junio C Hamano <gitster@pobox.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Daniel Barkalow <barkalow@iabervon.org>, git@vger.kernel.org
Subject: Re: [PATCH] Add support for host aliases in config files
Date: Fri, 25 Jan 2008 11:01:12 -0800 [thread overview]
Message-ID: <7vabmt7mrr.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <m3fxwlagbu.fsf@localhost.localdomain> (Jakub Narebski's message of "Fri, 25 Jan 2008 10:52:27 -0800 (PST)")
Jakub Narebski <jnareb@gmail.com> writes:
> From this I could not get how those configuration are meant to be
> used. Perhaps some usage example?
>
> BTW. wouldn't the same be solved better by enabling remote.<name>.url
> to be multi-valued, first working for fetch, all URLs for push?
I think that is already the case. "git-remote" currently has an
annoying bug I haven't bothered to look into that makes the
command complain when remote.$nick.url has more than one values.
Worse, it complains _twice_ (or N-1 times for a remote that has
N URLs).
: gitster git.git/master; git remote
Warning: more than one remote.builders.url
Warning: more than one remote.builders.url
builders
gfi
git-gui
gitk
git-p4
git-svn
jbf-um
ko
ko-private
mingw
origin
repo
spearce.git
wing-fc5
wing-fc7
wing-fc8
Here, "builders" remote has 3 URLs because I wanted to use it to
push to 3 machines on which I build binary releases.
next prev parent reply other threads:[~2008-01-25 19:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 18:39 [PATCH] Add support for host aliases in config files Daniel Barkalow
2008-01-25 18:52 ` Jakub Narebski
2008-01-25 19:01 ` Junio C Hamano [this message]
2008-01-25 19:09 ` Daniel Barkalow
2008-01-25 19:33 ` Jakub Narebski
2008-01-25 19:53 ` Daniel Barkalow
2008-01-25 21:51 ` Jakub Narebski
2008-01-25 20:19 ` Junio C Hamano
2008-01-25 21:12 ` Daniel Barkalow
2008-01-25 21:48 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2008-02-17 18:38 Daniel Barkalow
2008-02-17 18:48 ` Jakub Narebski
2008-02-17 18:58 ` Daniel Barkalow
2008-02-17 19:36 ` Johannes Schindelin
2008-02-18 4:52 ` Junio C Hamano
2008-02-18 19:29 ` Daniel Barkalow
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=7vabmt7mrr.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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).