git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: 周应天 <zhoudao200@126.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Git log command doesn't run as expected.
Date: Tue, 10 Jul 2018 14:18:12 +0200	[thread overview]
Message-ID: <CACBZZX7_iiVu6scdpc4z-rG3wwjC-cwwOOO88vjwKGYqe2FTWQ@mail.gmail.com> (raw)
In-Reply-To: <F261A512-F38D-45F2-8F4F-A932B9BEA6A1@126.com>

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?

      reply	other threads:[~2018-07-10 12:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 11:16 Git log command doesn't run as expected 周应天
2018-07-10 12:18 ` Ævar Arnfjörð Bjarmason [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACBZZX7_iiVu6scdpc4z-rG3wwjC-cwwOOO88vjwKGYqe2FTWQ@mail.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=zhoudao200@126.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).