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

Re: Patterns work unexpectedly with "git log" commit limiting

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 17, 2008, 08:17 UTC
Message-ID
<7vhcaoj55u.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080717074706.GA5392@mithlond.arda.local>
Teemu Likonen <tlikonen@iki.fi> writes:
Show 5 quoted lines
>  1. Option order changes the behaviour. "git log" with
> ...
>  2. Internally --author= and --committer= fields contain more stuff than
> ...
>  3. What is the supposed behaviour of -F (--fixed-strings) when combined

I won't have time right now to comment on the previous three, because they are not my code (meaning, I need to dig around before I can intelligently answer -- maybe when I have free time). What you expected does sound very sensible, though.

>  4. Logical AND/OR operation.

The --grep and --author search of "log" family shares git-grep logical expression engine, so if you somehow can come up with a way to pass --and (or even better, --all-match) from the command line just like we can give them to git-grep, searching with combinations of and/or/not should be doable.

Previous: Teemu LikonenNext: Petr Baudis
Message 2 of 3 in “Patterns work unexpectedly with "git log" commit limiting”
  1. Teemu LikonenJul 17, 2008
  2. Junio C HamanoJul 17, 2008
  3. Petr BaudisJul 17, 2008

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.