From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Steven Walter <stevenrwalter@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation for git-log --follow
Date: Fri, 13 Jul 2007 15:47:19 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707131540490.14781@racer.site> (raw)
In-Reply-To: <20070712145230.GA21590@dervierte>
Hi,
On Thu, 12 Jul 2007, Steven Walter wrote:
> +--follow::
> + Continue listing the history of a file beyond renames.
> +
Maybe say "Follow the history of a file beyond renames"?
> @@ -91,6 +94,12 @@ git log -r --name-status release..test::
> in the "release" branch, along with the list of paths
> each commit modifies.
>
> +git log --follow builtin-rev-list.c::
> +
> + Shows the commits that changed builtin-rev-list.c, including
> + those commits that occurred before the file was given its
> + present name.
> +
This is not particularly clear IMHO. Probably it would be a good thing to
contrast vs no-follow:
The output of "git log builtin-rev-list.c" stops with commit
"v1.4.0-rc1~126", as if the file was created there.
With "--follow", git will detect that this file was renamed
from "rev-list.c" and minimally modified in that commit. After
this, it will continue with the log, using the file name
"rev-list.c".
Ciao,
Dscho
prev parent reply other threads:[~2007-07-13 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 14:52 [PATCH] Documentation for git-log --follow Steven Walter
2007-07-12 18:48 ` Linus Torvalds
2007-07-13 14:47 ` Johannes Schindelin [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=Pine.LNX.4.64.0707131540490.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=stevenrwalter@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.
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).