From: Jakub Narebski <jnareb@gmail.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Add support for host aliases in config files
Date: Fri, 25 Jan 2008 20:33:12 +0100 [thread overview]
Message-ID: <200801252033.13142.jnareb@gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0801251355490.13593@iabervon.org>
On Friday, 25 January 2008, Daniel Barkalow wrote:
> On Fri, 25 Jan 2008, Jakub Narebski wrote:
>> Daniel Barkalow <barkalow@iabervon.org> writes:
>>
>>> This allows users with different preferences for access methods to the
>>> same remote repositories to rewrite each other's URLs to get the
>>> desired access.
>>
>> [...]
>>> +host.<name>.base::
>>> + The base URL which should be used for this particular
>>> + host. This can be used by a user who has a better access
>>> + method to a repository than other users to make use of the
>>> + preferable path despite getting URLs from other users using
>>> + more commonly-available methods. Alternatively, a user who
>>> + only has less privileged access to a repository than the usual
>>> + audience can use this mechanism to replace disallowed methods
>>> + with public ones.
>>> +
>>> +host.<name>.alias::
>>> + Additional base URLs which refer to this host. If a URL
>>> + matches this, any access to it will use the URL formed with
>>> + the corresponding base URL instead of the given URL.
>>> +
>>
>> From this I could not get how those configuration are meant to be
>> used. Perhaps some usage example?
>
> [host "kernel"]
> base = git://git.kernel.org/pub/
> alias = git+ssh://master.kernel.org/pub/
> alias = master.kernel.org:/pub/
>
>> 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?
Ah, thanks. I have misunderstood the above description (hint, hint!)...
> The real point is actually for when you're dealing with URLs on the
> command line which you've cut-and-paste from email or other things. For
> example, the patches in the -mm quilt series say where the git trees are,
> but they're all like
> "git+ssh://master.kernel.org/pub/scm/linux/kernel/git/dtor/input.git",
> which is ideal for people (like Andrew) who have accounts on master, but
> requires manual fixing for people (like me) who don't.
>
> With the above config, I can do:
>
> git fetch git+ssh://master.kernel.org/pub/scm/linux/kernel/git/dtor/input.git
Couldn't you just configure "kernel" remote, and use "git fetch kernel"
instead?
> and it actually fetches
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git
>
> which actually works for me.
So this config variable is actually about _rewriting_ URLs, rather than
having multiple _alternate_ URLs to fetch from. IMHO either the
documentation above should be (re)written better (there is time, as we
are in feature freeze), or the example mentioned above should be added
(but where?).
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-01-25 19:33 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
2008-01-25 19:09 ` Daniel Barkalow
2008-01-25 19:33 ` Jakub Narebski [this message]
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=200801252033.13142.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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 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).