git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	しらいしななこ <nanako3@bluebottle.com>,
	git@vger.kernel.org, "Daniel Barkalow" <barkalow@iabervon.org>
Subject: Re: [PATCH 2/2] Add support for url aliases in config files
Date: Wed, 20 Feb 2008 21:19:31 -0500	[thread overview]
Message-ID: <76718490802201819g6e2662afjdcbbacadb2521106@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802201735030.7833@woody.linux-foundation.org>

On Wed, Feb 20, 2008 at 8:47 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:

>  So I think it really boils down to the fact that you want to "rewrite" the
>  thing. Not aliases, not "also known as", but you're logically really
>  looking for something like
>
>         [access "git://git.kernel.org/*"]
>                 proxy = proxy-program
>                 url = "ssh://master.kernel.org/*"
>
>  which admittedly looks rather strange too, but at the same time it does
>  make sense from a "what do we really want to do?" standpoint.
>
>  Of course, in this case Daniel didn't actually do that "proxy" part, but I
>  think the argument that we should try to make the config file syntax
>  describe what the user wants to do is still very true. So skip that
>  "proxy" part (maybe somebody wants to do that too some day), and leave the
>
>         [access "original"]
>                 url = "rewritten"
>
>  kind of syntax.
>
>  (And no, I'm not at all married to the "access" and "url" parts - I don't
>  care. I'm just saying that syntax should be tied to what people want to
>  do, not anything else.

Shrug:

[core]
  rewriterule = <from> <to>
  ; ...

If <from> or <to> contain whitespace then you have to use %20 or quotes.

(There is already proxy support elsewhere in the config.)

I think I'm done suggesting paint colors. :-)

j.

  reply	other threads:[~2008-02-21  2:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 18:43 [PATCH 2/2] Add support for url aliases in config files Daniel Barkalow
2008-02-20 19:15 ` Junio C Hamano
2008-02-20 19:24   ` Daniel Barkalow
2008-02-20 19:42     ` Junio C Hamano
2008-02-20 19:54       ` Jay Soffian
2008-02-20 20:42       ` Daniel Barkalow
2008-02-20 22:02       ` しらいしななこ
2008-02-20 22:22         ` Johannes Schindelin
2008-02-21  0:47           ` Junio C Hamano
2008-02-21  1:26             ` Jay Soffian
2008-02-21  1:47               ` Linus Torvalds
2008-02-21  2:19                 ` Jay Soffian [this message]
2008-02-21  5:04                 ` Daniel Barkalow
2008-02-21  5:34                   ` Junio C Hamano
2008-02-25  4:08                     ` Junio C Hamano
2008-02-25  4:30                       ` Daniel Barkalow
2008-02-25  6:22                         ` Junio C Hamano
2008-02-25  6:35                           ` Daniel Barkalow
2008-02-21 16:31                 ` Jon Loeliger
2008-02-20 19:49     ` Jay Soffian
2008-02-20 19:58       ` Junio C Hamano
2008-02-20 20:22         ` Jay Soffian

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=76718490802201819g6e2662afjdcbbacadb2521106@mail.gmail.com \
    --to=jaysoffian@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nanako3@bluebottle.com \
    --cc=torvalds@linux-foundation.org \
    /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).