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
Michael J Gruber <git@drmicha.warpmail.net>
Date
Jun 20, 2011, 11:08 UTC
Message-ID
<4DFF2A1D.3060206@drmicha.warpmail.net>
In-Reply-To
<20110620070316.GA15246@sigill.intra.peff.net>
Jeff King venit, vidit, dixit 20.06.2011 09:03:
Show 24 quoted lines
> 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
Previous: Jeff KingNext: Jeff King
Message 6 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.