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

Re: [PATCH] Add git-rev-list --invert-match

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 20, 2007, 04:05 UTC
Message-ID
<7vbqbym15x.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20070920025225.GA12076@jukie.net>
Show 21 quoted lines
> diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt
> index 7cd0e89..f7a4891 100644
> --- a/Documentation/git-rev-list.txt
> +++ b/Documentation/git-rev-list.txt
> @@ -29,6 +29,7 @@ SYNOPSIS
>  	     [ \--(author|committer|grep)=<pattern> ]
>  	     [ \--regexp-ignore-case | \-i ]
>  	     [ \--extended-regexp | \-E ]
> +	     [ \--invert-match ]
>  	     [ \--date={local|relative|default|iso|rfc|short} ]
>  	     [ [\--objects | \--objects-edge] [ \--unpacked ] ]
>  	     [ \--pretty | \--header ]
> @@ -238,6 +239,11 @@ limiting may be applied.
>  	Consider the limiting patterns to be extended regular expressions
>  	instead of the default basic regular expressions.
>  
> +--invert-match::
> +
> +	Show those parts of history that do not match any of the regular
> +        expression patterns.
> +
Tabs and spaces?

I am afraid people may not understand what "any of the regular expression patterns" means. How about being a bit more explicit, like this?

	When filtering the commits based on log message (`--grep`)
	or people (`--author` and `--committer`), show commits
	that do not match the criteria.
Previous: Bart TrojanowskiNext: Bart Trojanowski
Message 3 of 13 in “Add git-rev-list --invert-match”
  1. Add git-rev-list --invert-matchBart Trojanowski, Sep 19, 2007
  2. Add git-rev-list --invert-matchBart Trojanowski, Sep 20, 2007
  3. Junio C HamanoSep 20, 2007
  4. Bart TrojanowskiSep 20, 2007
  5. Johannes SchindelinSep 20, 2007
  6. Bart TrojanowskiSep 20, 2007
  7. Johannes SchindelinSep 20, 2007
  8. Junio C HamanoSep 20, 2007
  9. Johannes SchindelinSep 20, 2007
  10. [RFC] Add git-rev-list --not-(author|committer|grep)!=patternBart Trojanowski, Sep 22, 2007
  11. Jeff KingSep 21, 2007
  12. Johannes SchindelinSep 21, 2007
  13. Jeff KingSep 21, 2007

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.