From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jeff King <peff@peff.net>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Junio C Hamano <gitster@pobox.com>,
Boris Faure <billiob@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH/RFC] branch: add optional parameter to -r to specify remote
Date: Mon, 20 Jun 2011 13:08:13 +0200 [thread overview]
Message-ID: <4DFF2A1D.3060206@drmicha.warpmail.net> (raw)
In-Reply-To: <20110620070316.GA15246@sigill.intra.peff.net>
Jeff King venit, vidit, dixit 20.06.2011 09:03:
> On Mon, Jun 20, 2011 at 08:40:32AM +0200, Johannes Sixt wrote:
>
>>> $ git branch --match "jk/*"
>>>
>>> to show only local topic branches whose names match the given blob.
>>
>> I would hate having to learn a new syntax '--match "jk/*"' when we can
>> already say
>>
>> $ git log --remotes
>> $ git log --remotes=alice --remotes=bob
>> $ git log --remotes="jk/*"
>>
>> IMO, it is the right approach to have a long option --remotes with an
>> optional argument.
>
> For that matter, --match should be spelled "--glob", as we already have:
>
> $ git log --glob='jk/*'
>
> I think having the ref-selection for "git branch" match that of the
> revision walker makes sense.
>
> -Peff
Well, "branch" is about refs, and "log" about revs. I'd rather have
"branch" similar to "tag" in that respect (i.e. '-l'). I'm still meaning
to revive that series:
http://permalink.gmane.org/gmane.comp.version-control.git/172228
I've reworked a few more things compared to the RFC from back then but
was caught by lack of time and the rc phase. I'll send what I have asap.
Michael
next prev parent reply other threads:[~2011-06-20 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 19:19 [PATCH/RFC] branch: add optional parameter to -r to specify remote Boris Faure
2011-06-19 19:19 ` Boris Faure
2011-06-19 22:32 ` Junio C Hamano
2011-06-20 6:40 ` Johannes Sixt
2011-06-20 7:03 ` Jeff King
2011-06-20 11:08 ` Michael J Gruber [this message]
2011-06-20 13:09 ` Jeff King
2011-06-20 15:42 ` Junio C Hamano
2011-06-20 16:59 ` [PATCH] tag: accept multiple patterns for --list Jeff King
2011-06-20 15:49 ` [PATCH/RFC] branch: add optional parameter to -r to specify remote Junio C Hamano
2011-06-20 15:39 ` Junio C Hamano
2011-06-20 19:12 ` Boris Faure
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=4DFF2A1D.3060206@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=billiob@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--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 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.