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

Re: Inverting the --committer option to git-log with v1.7.5.4

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 26, 2012, 22:43 UTC
Message-ID
<7vr4qttgud.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAPRhCbuOsiHNOHJUTN8Na9qEqoTAbCb-G41WFscjYhDppKOLGg@mail.gmail.com>
"Todd A. Jacobs" <nospam+listmail@codegnome.org> writes:
> Is there currently a better way to request logs for "everyone but
> committer x" in Git? If not, is this a feature that someone who
> understands the Git source might find useful enough to add in?
No, there is not.

I wouldn't comment on the potential usefulness of such a feature, but I do not think there is anything fundamentally wrong to enhance the limited form of "--grep/--author/--committer" the "log" family of commands currently support to a full "grep boolean expressions" that is supported by "git grep" command to let you say something like:

	git log --author=rezrov --grep=nitfol \
        	--and \( --committer=xyzzy --or	--committer=frotz \) \
		--all --not master

to grab commits from all topics that are not yet merged to 'master', authored by rezrov and talks about nitfol, that are committed either by xyzzy or frotz.

The command line syntax to integrate the "grep boolean expressions" needs to be carefully thought out, as "--not" on the "log" family of commands is already used to mean something entirely different (it is a revision range operator), though.

Previous: Todd A. Jacobs
Message 2 of 2 in “Inverting the --committer option to git-log with v1.7.5.4”
  1. Todd A. JacobsAug 26, 2012
  2. Junio C HamanoAug 26, 2012

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.