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

[PATCH 1/4] directory-rename-detection.txt: update references to regression tests

From
Elijah Newren via GitGitGadget <gitgitgadget@gmail.com>
Date
Oct 15, 2020, 20:46 UTC
Message-ID
<03af0de2b689f94a5b464ba1618857f55cb8b1bf.1602794791.git.gitgitgadget@gmail.com>
In-Reply-To
<pull.879.git.git.1602794790.gitgitgadget@gmail.com>
From: Elijah Newren <newren@gmail.com>

The regression tests for directory rename detection were renamed from t6043 to t6423 in commit 919df31955 ("Collect merge-related tests to t64xx", 2020-08-10); update this file to match. Also, add a small clarification to nearby text while we're at it.

Signed-off-by: Elijah Newren <newren@gmail.com>
---
 Documentation/technical/directory-rename-detection.txt | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/technical/directory-rename-detection.txt b/Documentation/technical/directory-rename-detection.txt
index 844629c8c4..ce042cfcae 100644
--- a/Documentation/technical/directory-rename-detection.txt
+++ b/Documentation/technical/directory-rename-detection.txt
@@ -18,7 +18,8 @@ It is perhaps easiest to start with an example:
 More interesting possibilities exist, though, such as:
 
   * one side of history renames x -> z, and the other renames some file to
-    x/e, causing the need for the merge to do a transitive rename.
+    x/e, causing the need for the merge to do a transitive rename so that
+    the rename ends up at z/e.
 
   * one side of history renames x -> z, but also renames all files within x.
     For example, x/a -> z/alpha, x/b -> z/bravo, etc.
@@ -35,7 +36,7 @@ More interesting possibilities exist, though, such as:
     directory itself contained inner directories that were renamed to yet
     other locations).
 
-  * combinations of the above; see t/t6043-merge-rename-directories.sh for
+  * combinations of the above; see t/t6423-merge-rename-directories.sh for
     various interesting cases.
 
 Limitations -- applicability of directory renames
@@ -62,7 +63,7 @@ directory rename detection applies:
 Limitations -- detailed rules and testcases
 -------------------------------------------
 
-t/t6043-merge-rename-directories.sh contains extensive tests and commentary
+t/t6423-merge-rename-directories.sh contains extensive tests and commentary
 which generate and explore the rules listed above.  It also lists a few
 additional rules:
 
-- 
gitgitgadget
Previous: Elijah Newren via GitGitGadgetNext: Elijah Newren via GitGitGadget
Message 4 of 6 in “Directory rename detection testcases and rules”
  1. 0/4 Directory rename detection testcases and rulesElijah Newren via GitGitGadget, Oct 15, 2020
  2. 3/4 t6423: update directory rename detection tests with new ruleElijah Newren via GitGitGadget, Oct 15, 2020
  3. 4/4 t6423: more involved rules for renaming directories into each otherElijah Newren via GitGitGadget, Oct 15, 2020
  4. 1/4 directory-rename-detection.txt: update references to regression testsElijah Newren via GitGitGadget, Oct 15, 2020
  5. 2/4 t6423: more involved directory rename testElijah Newren via GitGitGadget, Oct 15, 2020
  6. Eric SunshineOct 15, 2020

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.