{"thread":{"id":"23807","subject":"What does the 100 in R100 mean?","startedAt":"2010-05-14T11:21:45Z","lastAt":"2010-05-14T12:20:52Z","messageCount":2,"participants":["Todd A. Jacobs","Thomas Rast"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"141665","messageId":"20100514112145.GQ12846@penguin.codegnome.org","threadId":"23807","inReplyTo":null,"subject":"What does the 100 in R100 mean?","fromName":"Todd A. Jacobs","fromEmail":"nospam@codegnome.org","sentAt":"2010-05-14T11:21:45Z","receivedAt":"2010-05-14T11:21:45Z","isPatch":false,"sender":{"key":"nospam@codegnome.org","avatar":null},"body":"When I'm looking at the output for renamed files in git-log or\ngit-whatchanged, renamed files always seem to say \"R100.\" So, I looked\nin the man page, followed the internal references to --diff-filter, and\nremain stumped as to what the digits stand for. I couldn't even find an\nexplanatory comment in the git source code.\n\nObviously, R is for \"(R)enamed.\" What is the \"100\" for? If it's being\nreturned as a flag to --name-status and friends, it should probably be\ndocumented somewhere.\n\n-- \n\"Oh, look: rocks!\"\n\t-- Doctor Who, \"Destiny of the Daleks\"\n"},{"id":"141667","messageId":"201005141420.52657.trast@student.ethz.ch","threadId":"23807","inReplyTo":"20100514112145.GQ12846@penguin.codegnome.org","subject":"Re: What does the 100 in R100 mean?","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2010-05-14T12:20:52Z","receivedAt":"2010-05-14T12:20:52Z","isPatch":false,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Todd A. Jacobs wrote:\n> When I'm looking at the output for renamed files in git-log or\n> git-whatchanged, renamed files always seem to say \"R100.\" So, I looked\n> in the man page, followed the internal references to --diff-filter, and\n> remain stumped as to what the digits stand for. I couldn't even find an\n> explanatory comment in the git source code.\n> \n> Obviously, R is for \"(R)enamed.\" What is the \"100\" for? If it's being\n> returned as a flag to --name-status and friends, it should probably be\n> documented somewhere.\n\nIt is, but in the \"wrong\" section:\n\nRAW OUTPUT FORMAT\n[...]\n       Possible status letters are:\n       ·   A: addition of a file\n       ·   C: copy of a file into a new one\n       ·   D: deletion of a file\n       ·   M: modification of the contents or mode of a file\n       ·   R: renaming of a file\n[...]\n       Status letters C and R are always followed by a score (denoting\n       the percentage of similarity between the source and target of\n       the move or copy), and are the only ones to be so.\n\nThe patch below might rectify that, but it's not that reader-friendly\nbecause it has to point at the git-diff manpage where diff-format.txt\nis not included.  The ifdef is also an incomplete test because\ndiff-{files,index,tree} include diff-format.txt but don't set\ngit-diff.\n\ndiff --git i/Documentation/diff-options.txt w/Documentation/diff-options.txt\nindex 98cc779..424971c 100644\n--- i/Documentation/diff-options.txt\n+++ w/Documentation/diff-options.txt\n@@ -107,8 +107,12 @@ any of those replacements occurred.\n \tShow only names of changed files.\n \n --name-status::\n-\tShow only names and status of changed files. See the description\n-\tof the `--diff-filter` option on what the status letters mean.\n+\tShow only names and status of changed files. See the \"RAW\n+\tOUTPUT FORMAT\" section\n+ifndef::git-diff[]\n+\tin linkgit:git-diff[1]\n+endif::git-diff[]\n+\tfor what the status codes mean.\n \n --submodule[=<format>]::\n \tChose the output format for submodule differences. <format> can be one of\n\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"}]}