After vainly searching the Documentation for how to follow renames, I finally broke down and grepped the source. It would appear that Linus didn't add write and docs for this feature when he wrote it. The following patch rectifies that, hopefully sparing future users from resorting to the source code. Signed-off-by: Steven Walter <stevenrwalter@xxxxxxxxx> --- Documentation/git-log.txt | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt index 7adcdef..63c1dbe 100644 --- a/Documentation/git-log.txt +++ b/Documentation/git-log.txt @@ -61,6 +61,9 @@ include::pretty-options.txt[] the specified paths; this means that "<paths>..." limits only commits, and doesn't limit diff for those commits. +--follow:: + Continue listing the history of a file beyond renames. + <paths>...:: Show only commits that affect the specified paths. @@ -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. + Discussion ---------- -- 1.5.3.rc0 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
