aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-10-15 14:51:08 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-10-15 14:51:08 -0400
commit9dff858a97af7f97d1a37d16dae4267918d877e8 (patch)
tree62790133758815f7ffeedbb1d61e92349918c5a3
parentad0c963938482f40740b4ee214e0edf0b5e4bf17 (diff)
response
-rw-r--r--doc/walkthrough/renaming_files/comment_3_6b579a4f2990a28b33a8170ebd39da5c._comment15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/walkthrough/renaming_files/comment_3_6b579a4f2990a28b33a8170ebd39da5c._comment b/doc/walkthrough/renaming_files/comment_3_6b579a4f2990a28b33a8170ebd39da5c._comment
new file mode 100644
index 000000000..a5edbcf2d
--- /dev/null
+++ b/doc/walkthrough/renaming_files/comment_3_6b579a4f2990a28b33a8170ebd39da5c._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2015-10-15T18:46:50Z"
+ content="""
+This is basically the same as thinking that git should change the SHA1
+used to refer to a file in the repository just because it was renamed.
+That does not normally make sense.
+
+Including the original extension in the git-annex key is done to avoid
+confusing some poorly-behaved programs that expect to follow the symlink
+and find a file with an extension. It's best to ignore the extension part
+of the key, or if you like, you can change the [[backend|doc/backends]] from SHA256E to
+SHA256, and then new keys won't include that extension.
+"""]]