From: Theodore Tso <tytso@mit.edu>
To: Junio C Hamano <junkio@cox.net>
Cc: Pavel Roskin <proski@gnu.org>, git@vger.kernel.org
Subject: Re: [PATCH] git-remote: support remotes with a dot in the name
Date: Wed, 21 Feb 2007 05:21:11 -0500 [thread overview]
Message-ID: <20070221102111.GB19825@thunk.org> (raw)
In-Reply-To: <7vfy90t4mo.fsf@assigned-by-dhcp.cox.net>
On Tue, Feb 20, 2007 at 10:18:55PM -0800, Junio C Hamano wrote:
> Do you mean:
>
> [remote "wireless-2.6.url"]
> url = wire.less:/repo/sito/ry.git
> fetch = +refs/heads/*:refs/remotes/wireless-2.6.url/*
Or even more likely:
[remote "stable-2.6.19"]
url = git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.19.y.git
fetch = +refs/heads/*:refs/remotes/stable-2.6.19/*
> If so I think my replacement would match it. It will be
> returned from "git config --get-regexp '^remote\.'" like this:
>
> remote.wireless-2.6.url.url wire.less:/repo/sito/ry.git
> remote.wireless-2.6.url.fetch +refs/heads/*:refs/remotes/wireless-2.6.url/*
>
> and in:
>
> /^remote\.(\S+?)\.([^.\s]+)\s+(.*)$/
>
> $1 would match shortest non-whitespace sequence after "remote.",
> $2 would match longuest non-dot, non-whitespace sequence before
> a sequence of whitespaces, and
> $3 would match everything after that sequence of whitespaces.
>
> So, $1 = "wireless-2.6.url", $2 = "url", $3 = "wire.less:/repo/sito/ry.git"
> or $1 = "wireless-2.6.url", $2 = "fetch", $3 = "+refs/heads/...."
>
> But my Perl is rusty, so please double check it.
Yep, looks good to me.
- Ted
prev parent reply other threads:[~2007-02-21 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 5:03 [PATCH] git-remote: support remotes with a dot in the name Pavel Roskin
2007-02-21 5:21 ` Junio C Hamano
2007-02-21 5:46 ` Pavel Roskin
2007-02-21 6:18 ` Junio C Hamano
2007-02-21 7:12 ` Pavel Roskin
2007-02-21 7:29 ` Shawn O. Pearce
2007-02-21 7:32 ` Junio C Hamano
2007-02-21 10:21 ` Theodore Tso [this message]
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=20070221102111.GB19825@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=proski@gnu.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 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.