git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Document git-blame triple -C option

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Jan 8, 2010, 14:10 UTC
Message-ID
<f3271551001080610p62ef6abfge1c96648d1ea948f@mail.gmail.com>
The git-blame -CCC option is undocumented. This patch fixes that.
From 2732bf40f7607941ce1d65ce4d0effc0e8a0a593 Mon Sep 17 00:00:00 2001
From: Ramkumar Ramachandra <artagnon@gmail.com>
Date: Fri, 8 Jan 2010 19:29:02 +0530
Subject: [PATCH] Document git-blame triple -C option

git-blame -CCC is explained in builin-blame.c line 2171, but is unexplained in the documentation. This patch fixes that.

Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
---
 Documentation/blame-options.txt |   13 +++++++------
 Documentation/git-blame.txt     |    2 +-
 2 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/Documentation/blame-options.txt b/Documentation/blame-options.txt
index 1625ffc..e1abf1e 100644
--- a/Documentation/blame-options.txt
+++ b/Documentation/blame-options.txt
@@ -94,12 +94,13 @@ within a file for it to associate those lines with the parent
 commit.
 
 -C|<num>|::
-	In addition to `-M`, detect lines copied from other
-	files that were modified in the same commit.  This is
-	useful when you reorganize your program and move code
-	around across files.  When this option is given twice,
-	the command additionally looks for copies from all other
-	files in the parent for the commit that creates the file.
+	In addition to `-M`, detect lines copied from other files that
+	were modified in the same commit.  This is useful when you
+	reorganize your program and move code around across files.
+	When this option is given twice, the command additionally
+	looks for copies from other files in the commit that creates
+	the file. When this option is given thrice, the command
+	additionally looks for copies from other files in any commit.
 +
 <num> is optional but it is the lower bound on the number of
 alphanumeric characters that git must detect as moving
diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt
index 8c7b7b0..25bc416 100644
--- a/Documentation/git-blame.txt
+++ b/Documentation/git-blame.txt
@@ -9,7 +9,7 @@ SYNOPSIS
 --------
 [verse]
 'git blame' [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-p] [-w] [--incremental] [-L n,m]
-            [-S <revs-file>] [-M] [-C] [-C] [--since=<date>]
+            [-S <revs-file>] [-M] [-C] [-C] [-C] [--since=<date>]
 	    [<rev> | --contents <file> | --reverse <rev>] [--] <file>
 
 DESCRIPTION
-- 
1.6.5
Next: Michael J Gruber
Message 1 of 3 in “Document git-blame triple -C option”
  1. Document git-blame triple -C optionRamkumar Ramachandra, Jan 8, 2010
  2. Michael J GruberJan 8, 2010
  3. Ramkumar RamachandraJan 8, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.