* Git log command doesn't run as expected.
@ 2018-07-10 11:16 周应天
2018-07-10 12:18 ` Ævar Arnfjörð Bjarmason
0 siblings, 1 reply; 2+ messages in thread
From: 周应天 @ 2018-07-10 11:16 UTC (permalink / raw)
To: git
Hi,
I’m using following command to do some search work:
git log --all -G 'some regexp' -p — path/to/my/file.
But the output could miss some commit. (For example, I grep a little piece of code from a commit diff message(properly handled for regexp), but when I use the command above to search that code, I could not get that commit.)
I wonder that it is because I use it in a wrong way? Then what should I do to correct it.
Thanks!
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Git log command doesn't run as expected.
2018-07-10 11:16 Git log command doesn't run as expected 周应天
@ 2018-07-10 12:18 ` Ævar Arnfjörð Bjarmason
0 siblings, 0 replies; 2+ messages in thread
From: Ævar Arnfjörð Bjarmason @ 2018-07-10 12:18 UTC (permalink / raw)
To: 周应天; +Cc: Git Mailing List
On Tue, Jul 10, 2018 at 1:16 PM, 周应天 <zhoudao200@126.com> wrote:
> Hi,
> I’m using following command to do some search work:
> git log --all -G 'some regexp' -p — path/to/my/file.
> But the output could miss some commit. (For example, I grep a little piece of code from a commit diff message(properly handled for regexp), but when I use the command above to search that code, I could not get that commit.)
> I wonder that it is because I use it in a wrong way? Then what should I do to correct it.
Have you tried with --full-history? Does that find what you're looking for?
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-07-10 12:18 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-07-10 11:16 Git log command doesn't run as expected 周应天
2018-07-10 12:18 ` Ævar Arnfjörð Bjarmason
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).