From: Kevin Daudt <me@ikke.info>
To: Chris Packham <judge.packham@gmail.com>
Cc: GIT <git@vger.kernel.org>
Subject: Re: git log FILE vs git log --follow FILE missing commits
Date: Sun, 2 Feb 2020 22:42:43 +0100 [thread overview]
Message-ID: <20200202214243.GA1090206@alpha> (raw)
In-Reply-To: <CAFOYHZAx-MM26AuJmscK=kGgukQ62vkyqAqU49U-5WRaTp4mGQ@mail.gmail.com>
On Mon, Feb 03, 2020 at 10:27:52AM +1300, Chris Packham wrote:
> Hi,
>
> I've just hit a problem where git log doesn't want to tell me about a
> commit that touches a specific file.
>
> I wanted to point someone at a particular change that I knew was made
> to a file so I fired up 'git log FILE' and to my surprise it wasn't
> listed. I wondered if I had remembered wrong so went grepping to
> confirm the change was in the file I thought it was, sure enough it
> was there.
>
> Poking around a bit I found that git log --follow FILE shows the
> intended commit but git log FILE doesn't (it does show other commits
> that touch the file, most of which have tags if that's significant).
> The file hasn't been renamed so I didn't really expect --follow to
> change any behavior.
>
> The version of git I'm using is 2.25.0 from
> http://ppa.launchpad.net/git-core/ppa/ubuntu bionic main. I also tried
> 2.24.1 and 2.23.1 with the same problem.
>
> Any suggestions for tracking this down?
>
> Thanks,
> Chris
Hey Chris,
Try `git log --full-history FILE`. When passing a path to `git log` will
enable history simplification, which might explain why certain commits
are not shown.
Kind regards, Kevin.
next prev parent reply other threads:[~2020-02-02 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 21:27 git log FILE vs git log --follow FILE missing commits Chris Packham
2020-02-02 21:42 ` Kevin Daudt [this message]
2020-02-02 21:53 ` Chris Packham
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200202214243.GA1090206@alpha \
--to=me@ikke.info \
--cc=git@vger.kernel.org \
--cc=judge.packham@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).