From: Junio C Hamano <gitster@pobox.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: git@vger.kernel.org
Subject: Re: git log -- <old path> not working
Date: Wed, 17 Jun 2020 13:18:36 -0700 [thread overview]
Message-ID: <xmqqlfkltpib.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200615212521.GT6112@intel.com> ("Ville Syrjälä"'s message of "Tue, 16 Jun 2020 00:25:21 +0300")
Ville Syrjälä <ville.syrjala@linux.intel.com> writes:
> $ git log -- drivers/acpi/configfs.c
> -> nothing
>
> $ git log --follow -- drivers/acpi/configfs.c
> $ git log --full-history -- drivers/acpi/configfs.c
> -> works
>
> First time I've seen this fail. Expected behaviour for
> some reason, or a bug?
Expected.
In a history is branchy and mergy,
---O---o---o---o---o---M---x
\ /
o---A---o---B---o
where A, B and possibly M made changes to PATH,
$ git log X -- PATH
may show nothing if the PATH at O and M are identical. This is
described in "History Simplification" section of "git log --help"
prev parent reply other threads:[~2020-06-17 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 21:25 git log -- <old path> not working Ville Syrjälä
2020-06-17 20:18 ` Junio C Hamano [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=xmqqlfkltpib.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ville.syrjala@linux.intel.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).