From: Junio C Hamano <gitster@pobox.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Jeff King <peff@peff.net>, Jim Garrison <jim.garrison@nwea.org>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Globbing for ignored branches?
Date: Fri, 24 Jan 2014 12:44:58 -0800 [thread overview]
Message-ID: <xmqqmwilqfcl.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140124203312.GF396@x4> (Markus Trippelsdorf's message of "Fri, 24 Jan 2014 21:33:12 +0100")
Markus Trippelsdorf <markus@trippelsdorf.de> writes:
> On 2014.01.24 at 12:00 -0800, Junio C Hamano wrote:
>> Jeff King <peff@peff.net> writes:
>>
>> > On Fri, Jan 24, 2014 at 07:32:22PM +0100, Markus Trippelsdorf wrote:
>> >
>> >> > However, you do have to specify each branch individually. You probably
>> >> > want to say "all branches except X", and you cannot currently specify
>> >> > a negative refspec like that.
>> >>
>> >> Yes, that was the question I wanted to ask (, sorry for not formulating
>> >> it more clearly).
>> >> Is this "negative refspec for branches" a feature that is planned for
>> >> the future?
>> >
>> > It is something that has been talked about before, but I do not think
>> > anybody is actively working on. It would probably not be too hard a
>> > feature if you are interested in getting your feet wet in git
>> > development. :)
>>
>> The end result might be not so hard in the mechanical sense, but
>> designing the interface would be hard. I do not offhand think of a
>> good way to do this.
>
> I don't know if the in-tree regex engine supports negative lookaheads.
> If it does, then something like the following should work (to use my
> "hjl" example):
>
> ^(.(?!hjl))*
refspec wildcards are *NOT* regular expressions.
next prev parent reply other threads:[~2014-01-24 20:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 9:01 Globbing for ignored branches? Markus Trippelsdorf
2014-01-24 16:37 ` Jim Garrison
2014-01-24 17:07 ` Markus Trippelsdorf
2014-01-24 17:09 ` Markus Trippelsdorf
2014-01-24 18:23 ` Jeff King
2014-01-24 18:32 ` Markus Trippelsdorf
2014-01-24 18:55 ` Jeff King
2014-01-24 20:00 ` Junio C Hamano
2014-01-24 20:33 ` Markus Trippelsdorf
2014-01-24 20:44 ` Junio C Hamano [this message]
2014-01-24 20:52 ` Markus Trippelsdorf
2014-01-24 20:48 ` Jeff King
2014-01-24 21:08 ` Junio C Hamano
2014-01-25 1:34 ` Jeff King
2014-01-25 14:15 ` Markus Trippelsdorf
2014-01-25 17:15 ` Markus Trippelsdorf
2014-01-25 20:02 ` Jeff King
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=xmqqmwilqfcl.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jim.garrison@nwea.org \
--cc=markus@trippelsdorf.de \
--cc=peff@peff.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).