All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Pavel Roskin <proski@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-remote: support remotes with a dot in the name
Date: Tue, 20 Feb 2007 23:32:06 -0800	[thread overview]
Message-ID: <7vr6skrmo9.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070221021206.8onspw0840gcs8ck@webmail.spamcop.net> (Pavel Roskin's message of "Wed, 21 Feb 2007 02:12:06 -0500")

Pavel Roskin <proski@gnu.org> writes:

> I was thinking of something like
>
> [remote "wireless-2.6"]
> url = http://foo/bar
> url.push = ssh://foo/bar

Ahh.

I was not taking the above use case into account when I wrote
that regexp, because I do not think we ever supported (nor were
planning to ever support) names with dot at the third level.

> But I think it's quite unlikely to be named like that.

The second level ("wireless-2.6") is designed to be more lenient
to accept wider "user level names" for branches, remotes, etc.,
but the third level is for variable names the programs use, and
it is not the question of likely/unlikely, but more about how we
(as the git system builders, not the end users) want to name our
variables.  So I do not think it is not such a big deal if we do
not support "url.push" variable.

>> But my Perl is rusty, so please double check it.
>
> The "(\S*?)" construct looks weird (you probably meant to use "(\S*)" for the
> remote name), but the rest is probably OK.  I'll send the "double-checked"
> patch tomorrow unless you beat me at that.

Actually I did mean to write "*?"; wasn't it how minimal match
is written?

  parent reply	other threads:[~2007-02-21  7:32 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 [this message]
2007-02-21 10:21       ` Theodore Tso

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=7vr6skrmo9.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --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.