From: Junio C Hamano <gitster@pobox.com>
Date: Tue, 29 Jan 2008 20:03:06 GMT
Subject: Re: Can git log <file> follow log of its origins?
Message-ID: <7v63xco0w5.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <333479.13589.qm@web45901.mail.sp1.yahoo.com>

Max Pollard <ajaxsupremo@yahoo.com> writes:

> If I do the following:
>
>      $ git init
>      $ echo "The brown fox is getting old" > a.txt
>      $ git add a.txt
>      $ git commit -m "Commit a.txt"
>
>      $ cp a.txt b.txt
>      $ git add b.txt
>      $ git commit -m "Copy a.txt to b.txt"
>
>      $ git log b.txt
>
> I only see the log corresponding to the 2nd commit (v1.5.3.5).

That is what you are asking "git log" to show.  "git log b.txt"
means "please simplify the history by throwing away commits that
do not have changes to paths that match b.txt, and then show the
resulting log with the change pertaining to that path".  The
first commit does not change a path called b.txt (in other
words, "git show --stat HEAD^" will not give diffstat for "b.txt"),
so that commit is not shown.

$ git log --pretty=oneline --name-status -C -C