[git-users] Re: What's wrong with "git log --grep"?

Do not use the '=' On Friday, October 10, 2014 5:18:36 AM UTC-4, Marat Shakurov wrote: > > I doing: > > git log -p > > and see that optput contains string '*somestring1*' > > I doing: > git log -p --grep=somestring1 > or > git log -p --grep=somestring1 -i > or > git log -p --grep=somestring1 -i F

[git-users] Re: What's wrong with "git log --grep"?

On Friday, 10 October 2014 11:18:36 UTC+2, Marat Shakurov wrote: > > I doing: > > git log -p > > and see that optput contains string '*somestring1*' > > I doing: > git log -p --grep=somestring1 > or > git log -p --grep=somestring1 -i > or > git log -p --grep=somestring1 -i F > > and use qoutation m

[git-users] Re: What's wrong with "git log --grep"?

On Friday, October 10, 2014 2:18:36 AM UTC-7, Marat Shakurov wrote: > > I doing: > > git log -p > > and see that optput contains string '*somestring1*' > > I doing: > git log -p --grep=somestring1 > or > git log -p --grep=somestring1 -i > or > git log -p --grep=somestring1 -i F > Are you searchi

[git-users] Re: What's wrong with "git log --grep" ? How I can find a 'somestring1' in a whole log of the project's commits?

On Friday, 10 October 2014 11:01:03 UTC+2, Marat Shakurov wrote: > > how I can find a 'string' in a whole log of the project's commits > > I know there is: > git log -p --grep= > and some options > > I don't know as correctly it to use > > I absolutely know, that the log of my project contains the