Re: [PATCH] Documentation for git-log --follow

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jul 13, 2007, 14:47 UTC
Message-ID: <Pine.LNX.4.64.0707131540490.14781@racer.site>
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"?

Show 10 quoted lines

> @@ -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