summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar http://christian.amsuess.com/chrysn <chrysn@web>2011-03-09 23:47:49 +0000
committerGravatar admin <admin@branchable.com>2011-03-09 23:47:49 +0000
commit4163341c9d09f92f4bd5dfb5d2f34538bee51bdb (patch)
treec24a8046919bd582e8118f4277612699d27b8315 /doc
parent9229d182d32570f6829ced655aa673ceddfe7693 (diff)
Added a comment: use mini-branches
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/git_rename_detection_on_file_move/comment_1_0531dcfa833b0321a7009526efe3df33._comment26
1 files changed, 26 insertions, 0 deletions
diff --git a/doc/bugs/git_rename_detection_on_file_move/comment_1_0531dcfa833b0321a7009526efe3df33._comment b/doc/bugs/git_rename_detection_on_file_move/comment_1_0531dcfa833b0321a7009526efe3df33._comment
new file mode 100644
index 000000000..8fec6bad7
--- /dev/null
+++ b/doc/bugs/git_rename_detection_on_file_move/comment_1_0531dcfa833b0321a7009526efe3df33._comment
@@ -0,0 +1,26 @@
+[[!comment format=mdwn
+ username="http://christian.amsuess.com/chrysn"
+ nickname="chrysn"
+ subject="use mini-branches"
+ date="2011-03-09T23:47:48Z"
+ content="""
+if you go for the two-commits version, small intermediate branches (or git-commit-tree) could be used to create a tree like this:
+
+
+ * commit 106eef2
+ |\ Merge: 436e46f 9395665
+ | |
+ | | the main commit
+ | |
+ | * commit 9395665
+ |/
+ | intermediate move
+ |
+ * commit 436e46f
+ |
+ | ...
+
+while the first commit (436e46f) has a \"`/subdir/foo → ../.git-annex/where_foo_is`\", the intermediate (9395665) has \"`/subdir/deeper/foo → ../.git-annex/where_foo_is`\", and the inal commit (106eef2) has \"`/subdir/deeper/foo → ../../.git-annex/where_foo_is`\".
+
+`--follow` uses the intermediate commit to find the history, but the intermediate commit would neither show up in `git log --first-parent` nor affect `git diff HEAD^..` & co. (there could still be confusion over `git show`, though).
+"""]]