From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Jay Soffian <jaysoffian@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC] Refspec patterns with * in the middle
Date: Mon, 02 Mar 2009 15:30:29 -0800 [thread overview]
Message-ID: <7vsklvlcyy.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0903021746140.19665@iabervon.org> (Daniel Barkalow's message of "Mon, 2 Mar 2009 18:00:57 -0500 (EST)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> The issue, in my case, is importing from a system where branches contain
> projects instead of projects containing branches (and everything is a
> single namespace). So I want to match an insane (for us) LHS with a sane
> RHS to get stuff into reasonable shape. I don't really care about any
> patterns where the branch identifier is multiple components, but I
> wouldn't be surprised if somebody did.
Isn't this just getting more and more insane? Is this really worth
supporting, I have to wonder...
> Oh, and it looks like "?" is reserved and currently unused, so we could
> have * match one or more full path components, and ? match partial path
> components.
Well, "?" is not allowed exactly because it often is used to match a
single character by things like for-each-ref.
next prev parent reply other threads:[~2009-03-02 23:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 23:42 [RFC] Refspec patterns with * in the middle Daniel Barkalow
2009-03-02 12:54 ` Jay Soffian
2009-03-02 17:08 ` Junio C Hamano
2009-03-02 18:01 ` Jay Soffian
2009-03-02 18:25 ` Daniel Barkalow
2009-03-02 22:07 ` Jay Soffian
2009-03-02 22:39 ` Junio C Hamano
2009-03-02 22:58 ` Jay Soffian
2009-03-02 23:00 ` Daniel Barkalow
2009-03-02 23:30 ` Junio C Hamano [this message]
2009-03-03 16:25 ` David Kastrup
2009-03-02 18:22 ` 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=7vsklvlcyy.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=jaysoffian@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 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.