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

[PATCH 01/34] Documentation/diff-config: fix description of diff.renames

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 3, 2016, 17:23 UTC
Message-ID
<1459704240-28792-1-git-send-email-gitster@pobox.com>
From: Matthieu Moy <Matthieu.Moy@imag.fr>

The description was misleading, since "set to any boolean value" include "set to false", and diff.renames=false does not enable basic detection, but actually disables it. Also, document that diff.renames only affects Porcelain.

Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 Documentation/diff-config.txt | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/Documentation/diff-config.txt b/Documentation/diff-config.txt
index 6eaa452..cf4a915 100644
--- a/Documentation/diff-config.txt
+++ b/Documentation/diff-config.txt
@@ -108,9 +108,13 @@ diff.renameLimit::
 	detection; equivalent to the 'git diff' option '-l'.
 
 diff.renames::
-	Tells Git to detect renames.  If set to any boolean value, it
-	will enable basic rename detection.  If set to "copies" or
-	"copy", it will detect copies, as well.
+	Whether and how Git detects renames.  If set to "false",
+	rename detection is disabled. If set to "true", basic rename
+	detection is enabled.  If set to "copies" or "copy", Git will
+	detect copies, as well.  Defaults to false.  Note that this
+	affects only 'git diff' Porcelain like linkgit:git-diff[1] and
+	linkgit:git-log[1], and not lower level commands such as
+	linkgit:git-diff-files[1].
 
 diff.suppressBlankEmpty::
 	A boolean to inhibit the standard behavior of printing a space
-- 
2.8.0-246-g1783343
Next: Junio C Hamano
Message 1 of 4 in “Documentation/diff-config: fix description of diff.renames”
  1. 01/34 Documentation/diff-config: fix description of diff.renamesJunio C Hamano, Apr 3, 2016
  2. 02/34 t4001-diff-rename: wrap file creations in a testJunio C Hamano, Apr 3, 2016
  3. Junio C HamanoApr 3, 2016
  4. Junio C HamanoApr 3, 2016

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.