git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH/RFC] branch: add optional parameter to -r to specify remote

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 20, 2011, 15:49 UTC
Message-ID
<7vwrggcxl6.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4DFF2A1D.3060206@drmicha.warpmail.net>
Michael J Gruber <git@drmicha.warpmail.net> writes:
Show 10 quoted lines
>> 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.

Not really. What "log" output by traversing is about revisions, but we are discussing how the command line argument discover the set of refs to feed into the underlying machinery that does different things in each of the command (branch just lists them without any traversal, log shows history leading to the commits). So I do not see any difference and I think it would be appropriate if we can use the same notation to specify both "I want to see all branches that match this pattern" and "I want to see history leading to all refs that match this pattern".

> I'd rather have
> "branch" similar to "tag" in that respect (i.e. '-l').

And "tag --glob='*'" also falls into the same class from that point of view: "I want to see all tags that match this pattern".

Thanks.
Previous: Jeff KingNext: Junio C Hamano
Message 10 of 12 in “branch: add optional parameter to -r to specify remote”
  1. branch: add optional parameter to -r to specify remoteBoris Faure, Jun 19, 2011
  2. branch: add optional parameter to -r to specify remoteBoris Faure, Jun 19, 2011
  3. Junio C HamanoJun 19, 2011
  4. Johannes SixtJun 20, 2011
  5. Jeff KingJun 20, 2011
  6. Michael J GruberJun 20, 2011
  7. Jeff KingJun 20, 2011
  8. Junio C HamanoJun 20, 2011
  9. tag: accept multiple patterns for --listJeff King, Jun 20, 2011
  10. Junio C HamanoJun 20, 2011
  11. Junio C HamanoJun 20, 2011
  12. Boris FaureJun 20, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.