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

Re: [PATCH/RFC v2 0/2] add regex match flags to git describe

From
MBMostyn Bramley-Moore <mostynb@opera.com>
Date
Dec 31, 2015, 00:08 UTC
Message-ID
<5684720B.40208@opera.com>
In-Reply-To
<CACsJy8ADrHW=Tr2Tx04NoAKP3MfP__Ndjut_G_7HitLPHKn46w@mail.gmail.com>
On 12/30/2015 10:52 AM, Duy Nguyen wrote:
Show 6 quoted lines
> What about not using command line options? We could go with something
> like pathspec magic. I think as long as we provide three options:
> literal, some pattern matching and backquote, then the user has enough
> flexibility to specify any set of refs. For pattern matching I'd
> prefer wildmatch. regex can be used via backquote, e.g. `for-each-ref
> | grep ...` (or teach for-each-ref about regex to avoid grep).

I don't think that would solve my immediate problem, unless git for-each-ref knew how to produce output in the same order that git describe searches. But perhaps I misunderstand what you're suggesting with the backquote/subshell.

-Mostyn.
-- 
Mostyn Bramley-Moore
TV and Connected Devices
Opera Software ASA
mostynb@opera.com
Previous: Duy NguyenNext: Mostyn Bramley-Moore
Message 8 of 14 in “add regex match flags to git describe”
  1. 0/2 add regex match flags to git describeMostyn Bramley-Moore, Dec 28, 2015
  2. 1/2 describe: add option to use perl-compatible regexes with --matchMostyn Bramley-Moore, Dec 28, 2015
  3. 2/2 describe: add basic and extended posix regex matching for completenessMostyn Bramley-Moore, Dec 28, 2015
  4. Junio C HamanoDec 28, 2015
  5. Mostyn Bramley-MooreDec 29, 2015
  6. Junio C HamanoDec 29, 2015
  7. Duy NguyenDec 30, 2015
  8. Mostyn Bramley-MooreDec 31, 2015
  9. Mostyn Bramley-MooreDec 31, 2015
  10. Junio C HamanoDec 31, 2015
  11. Mostyn Bramley-MooreDec 31, 2015
  12. Junio C HamanoJan 4, 2016
  13. Mostyn Bramley-MooreJan 6, 2016
  14. Duy NguyenJan 6, 2016

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.