Re: git log: invert --author and --committer

Per Cederqvist writes: > I think it does make sense to document this with the --author/--committer > options. > > That wording would however make me assume that --all-match could also > be used, so that > > git log --all-match --author ceder --author cibot > > would list

Re: git log: invert --author and --committer

Per Cederqvist writes: > "can also be used to affect", right? (I think the word "to" is missing.) Correct. > That wording would however make me assume that --all-match could also > be used, so that > > git log --all-match --author ceder --author cibot > > would list

Re: git log: invert --author and --committer

On Mon, May 23, 2016 at 9:26 PM, Junio C Hamano wrote: > Junio C Hamano writes: > >> Per Cederqvist writes: >> >>> git log --invert-grep --author cibot >>... >> Yeah, the author/committer search piggy-backs the more generic "grep >> in

Re: git log: invert --author and --committer

Junio C Hamano writes: > Per Cederqvist writes: > >> git log --invert-grep --author cibot >... > Yeah, the author/committer search piggy-backs the more generic "grep > in the log" machinery, but it is quite hidden and the document > failed to tell the

Re: git log: invert --author and --committer

Per Cederqvist writes: > We have a repository that mostly contains configuration data. > This is updated by our continuous integration build system, but > every once in a while there are also more interesting commits > made by humans. > > For several years I have suffered in

git log: invert --author and --committer

We have a repository that mostly contains configuration data. This is updated by our continuous integration build system, but every once in a while there are also more interesting commits made by humans. For several years I have suffered in silence, wishing for a way to do something like git