git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: "Todd A. Jacobs" <nospam@codegnome.org>
Cc: <git@vger.kernel.org>
Subject: Re: What does the 100 in R100 mean?
Date: Fri, 14 May 2010 14:20:52 +0200	[thread overview]
Message-ID: <201005141420.52657.trast@student.ethz.ch> (raw)
In-Reply-To: <20100514112145.GQ12846@penguin.codegnome.org>

Todd A. Jacobs wrote:
> When I'm looking at the output for renamed files in git-log or
> git-whatchanged, renamed files always seem to say "R100." So, I looked
> in the man page, followed the internal references to --diff-filter, and
> remain stumped as to what the digits stand for. I couldn't even find an
> explanatory comment in the git source code.
> 
> Obviously, R is for "(R)enamed." What is the "100" for? If it's being
> returned as a flag to --name-status and friends, it should probably be
> documented somewhere.

It is, but in the "wrong" section:

RAW OUTPUT FORMAT
[...]
       Possible status letters are:
       ·   A: addition of a file
       ·   C: copy of a file into a new one
       ·   D: deletion of a file
       ·   M: modification of the contents or mode of a file
       ·   R: renaming of a file
[...]
       Status letters C and R are always followed by a score (denoting
       the percentage of similarity between the source and target of
       the move or copy), and are the only ones to be so.

The patch below might rectify that, but it's not that reader-friendly
because it has to point at the git-diff manpage where diff-format.txt
is not included.  The ifdef is also an incomplete test because
diff-{files,index,tree} include diff-format.txt but don't set
git-diff.

diff --git i/Documentation/diff-options.txt w/Documentation/diff-options.txt
index 98cc779..424971c 100644
--- i/Documentation/diff-options.txt
+++ w/Documentation/diff-options.txt
@@ -107,8 +107,12 @@ any of those replacements occurred.
 	Show only names of changed files.
 
 --name-status::
-	Show only names and status of changed files. See the description
-	of the `--diff-filter` option on what the status letters mean.
+	Show only names and status of changed files. See the "RAW
+	OUTPUT FORMAT" section
+ifndef::git-diff[]
+	in linkgit:git-diff[1]
+endif::git-diff[]
+	for what the status codes mean.
 
 --submodule[=<format>]::
 	Chose the output format for submodule differences. <format> can be one of


-- 
Thomas Rast
trast@{inf,student}.ethz.ch

      reply	other threads:[~2010-05-14 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14 11:21 What does the 100 in R100 mean? Todd A. Jacobs
2010-05-14 12:20 ` Thomas Rast [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=201005141420.52657.trast@student.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=nospam@codegnome.org \
    /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).