{"thread":{"id":"22130","subject":"[PATCH] Document git-blame triple -C option","startedAt":"2010-01-08T14:10:51Z","lastAt":"2010-01-08T18:58:52Z","messageCount":3,"participants":["Ramkumar Ramachandra","Michael J Gruber"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"131091","messageId":"f3271551001080610p62ef6abfge1c96648d1ea948f@mail.gmail.com","threadId":"22130","inReplyTo":null,"subject":"[PATCH] Document git-blame triple -C option","fromName":"Ramkumar Ramachandra","fromEmail":"artagnon@gmail.com","sentAt":"2010-01-08T14:10:51Z","receivedAt":"2010-01-08T14:10:51Z","isPatch":true,"sender":{"key":"r@artagnon.com","avatar":"https://avatars.githubusercontent.com/u/37226?v=4"},"body":"The git-blame -CCC option is undocumented. This patch fixes that.\n\n\nFrom 2732bf40f7607941ce1d65ce4d0effc0e8a0a593 Mon Sep 17 00:00:00 2001\nFrom: Ramkumar Ramachandra <artagnon@gmail.com>\nDate: Fri, 8 Jan 2010 19:29:02 +0530\nSubject: [PATCH] Document git-blame triple -C option\n\ngit-blame -CCC is explained in builin-blame.c line 2171, but is\nunexplained in the documentation. This patch fixes that.\n\nSigned-off-by: Ramkumar Ramachandra <artagnon@gmail.com>\n---\n Documentation/blame-options.txt |   13 +++++++------\n Documentation/git-blame.txt     |    2 +-\n 2 files changed, 8 insertions(+), 7 deletions(-)\n\ndiff --git a/Documentation/blame-options.txt b/Documentation/blame-options.txt\nindex 1625ffc..e1abf1e 100644\n--- a/Documentation/blame-options.txt\n+++ b/Documentation/blame-options.txt\n@@ -94,12 +94,13 @@ within a file for it to associate those lines with the parent\n commit.\n \n -C|<num>|::\n-\tIn addition to `-M`, detect lines copied from other\n-\tfiles that were modified in the same commit.  This is\n-\tuseful when you reorganize your program and move code\n-\taround across files.  When this option is given twice,\n-\tthe command additionally looks for copies from all other\n-\tfiles in the parent for the commit that creates the file.\n+\tIn addition to `-M`, detect lines copied from other files that\n+\twere modified in the same commit.  This is useful when you\n+\treorganize your program and move code around across files.\n+\tWhen this option is given twice, the command additionally\n+\tlooks for copies from other files in the commit that creates\n+\tthe file. When this option is given thrice, the command\n+\tadditionally looks for copies from other files in any commit.\n +\n <num> is optional but it is the lower bound on the number of\n alphanumeric characters that git must detect as moving\ndiff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt\nindex 8c7b7b0..25bc416 100644\n--- a/Documentation/git-blame.txt\n+++ b/Documentation/git-blame.txt\n@@ -9,7 +9,7 @@ SYNOPSIS\n --------\n [verse]\n 'git blame' [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-p] [-w] [--incremental] [-L n,m]\n-            [-S <revs-file>] [-M] [-C] [-C] [--since=<date>]\n+            [-S <revs-file>] [-M] [-C] [-C] [-C] [--since=<date>]\n \t    [<rev> | --contents <file> | --reverse <rev>] [--] <file>\n \n DESCRIPTION\n-- \n1.6.5\n\n"},{"id":"131096","messageId":"4B47510E.7040802@drmicha.warpmail.net","threadId":"22130","inReplyTo":"f3271551001080610p62ef6abfge1c96648d1ea948f@mail.gmail.com","subject":"Re: [PATCH] Document git-blame triple -C option","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2010-01-08T15:36:46Z","receivedAt":"2010-01-08T15:36:46Z","isPatch":true,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Ramkumar Ramachandra venit, vidit, dixit 08.01.2010 15:10:\n> The git-blame -CCC option is undocumented. This patch fixes that.\n\nAbove you see why it is difficult to comment on attached patches.\nThey're not included!\n\nYou re-wrapped the existing documentation. Please don't do that, because\nit makes it difficult to spot what you really changed.\n\nIt seems you added one sentence. Please don't use \"thrice\" for \"three\ntimes\", that is very old English and sounds funny.\n\nMichael\n"},{"id":"131116","messageId":"f3271551001081058l4fffa51t7ec52e9ce2f3166e@mail.gmail.com","threadId":"22130","inReplyTo":"4B47510E.7040802@drmicha.warpmail.net","subject":"Re: [PATCH] Document git-blame triple -C option","fromName":"Ramkumar Ramachandra","fromEmail":"artagnon@gmail.com","sentAt":"2010-01-08T18:58:52Z","receivedAt":"2010-01-08T18:58:52Z","isPatch":true,"sender":{"key":"r@artagnon.com","avatar":"https://avatars.githubusercontent.com/u/37226?v=4"},"body":"> Above you see why it is difficult to comment on attached patches.\n> They're not included!\n\nI'm sorry, but I'm behind a HTTP proxy, and GMail mangles up patches.\nI'm left with no choice but to attach the patches.\n\n> You re-wrapped the existing documentation. Please don't do that, because\n> it makes it difficult to spot what you really changed.\n\nOkay. Corrected.\n\n> It seems you added one sentence. Please don't use \"thrice\" for \"three\n> times\", that is very old English and sounds funny.\n\nOkay. I've also modified the second line (what happens when the option\nis given twice) for clarity.\n\n\nFrom 371705f64576ff7b8dc82bea19c714ce320097b9 Mon Sep 17 00:00:00 2001\nFrom: Ramkumar Ramachandra <artagnon@gmail.com>\nDate: Sat, 9 Jan 2010 00:18:07 +0530\nSubject: [PATCH v2] Document git-blame triple -C option\n\ngit-blame -CCC is explained in builin-blame.c line 2171, but is\nunexplained in the documentation. This patch fixes that.\n\nSigned-off-by: Ramkumar Ramachandra <artagnon@gmail.com>\n---\n Documentation/blame-options.txt |    6 ++++--\n Documentation/git-blame.txt     |    2 +-\n 2 files changed, 5 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/blame-options.txt b/Documentation/blame-options.txt\nindex 1625ffc..4833cac 100644\n--- a/Documentation/blame-options.txt\n+++ b/Documentation/blame-options.txt\n@@ -98,8 +98,10 @@ commit.\n \tfiles that were modified in the same commit.  This is\n \tuseful when you reorganize your program and move code\n \taround across files.  When this option is given twice,\n-\tthe command additionally looks for copies from all other\n-\tfiles in the parent for the commit that creates the file.\n+\tthe command additionally looks for copies from other\n+\tfiles in the commit that creates the file. When this\n+\toption is given three times, the command additionally\n+\tlooks for copies from other files in any commit.\n +\n <num> is optional but it is the lower bound on the number of\n alphanumeric characters that git must detect as moving\ndiff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt\nindex 8c7b7b0..b786471 100644\n--- a/Documentation/git-blame.txt\n+++ b/Documentation/git-blame.txt\n@@ -9,7 +9,7 @@ SYNOPSIS\n --------\n [verse]\n 'git blame' [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-p] [-w] [--incremental] [-L n,m]\n-            [-S <revs-file>] [-M] [-C] [-C] [--since=<date>]\n+\t    [-S <revs-file>] [-M] [-C] [-C] [-C] [--since=<date>]\n \t    [<rev> | --contents <file> | --reverse <rev>] [--] <file>\n \n DESCRIPTION\n-- \n1.6.5\n\n"}]}