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

Re: [BUG] git rev-parse :/ "regex" syntax not really regex?

From
Andreas Schwab <schwab@linux-m68k.org>
Date
Apr 17, 2016, 14:10 UTC
Message-ID
<87inzgtjfv.fsf@linux-m68k.org>
In-Reply-To
<20160417133741.GA28931@rhlx01.hs-esslingen.de>
Andreas Mohr <andi@lisas.de> writes:
> Unless I happened to misunderstand git's regex flavour, or something else...
> (hmm, perhaps it's a try-match-single-line vs. multi-line content issue,
> which perhaps does not work by specifying the trailing $)

This is exactly the difference. git log --grep matches individual lines (like grep), whereas :/<regexp> matches against the whole commit message including embedded (and trailing) newlines, and $ doesn't match an embedded newline. Thus to address the second commit in your example you have to use $':/^My commit\n' (using bash's ANSI-C quoting feature).

Andreas.
-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Previous: Andreas MohrNext: Andreas Mohr
Message 2 of 3 in “[BUG] git rev-parse :/ "regex" syntax not really regex?”
  1. Andreas MohrApr 17, 2016
  2. Andreas SchwabApr 17, 2016
  3. Andreas MohrApr 17, 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.