summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2017-03-02 14:04:15 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2017-03-02 14:04:15 -0400
commit544e6792d712f2e90e25776b3761e1c6d32e3059 (patch)
treee0f300f0dc519fd87caf3058959b30f46e63b21e /doc
parent754a90f70f3a2b7eb32a3658e309b73ad017e98e (diff)
comment
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/Dealing_with_long_filenames/comment_1_373798ea9763d3a0be5ce78f7e3f79f0._comment16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/forum/Dealing_with_long_filenames/comment_1_373798ea9763d3a0be5ce78f7e3f79f0._comment b/doc/forum/Dealing_with_long_filenames/comment_1_373798ea9763d3a0be5ce78f7e3f79f0._comment
new file mode 100644
index 000000000..32056270e
--- /dev/null
+++ b/doc/forum/Dealing_with_long_filenames/comment_1_373798ea9763d3a0be5ce78f7e3f79f0._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2017-03-02T18:01:51Z"
+ content="""
+It depends, is it failing because the filenames checked into git are too
+long? Or because the symlinks are links to too long paths?
+
+In the former case, you can `git rename` files as you like.
+As with any change you make to files in a git repository, that will
+propigate to other git repositories in the usual ways.
+
+In the latter case, you might be using a hash like SHA512 that causes
+problimatically long paths, and then `git annex migrate --backend=SHA256` might
+help.
+"""]]