From e4bcfcb618d0473d856c961127433d38341a03cf Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 2 Mar 2017 14:04:15 -0400 Subject: [PATCH] comment --- ...t_1_373798ea9763d3a0be5ce78f7e3f79f0._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/Dealing_with_long_filenames/comment_1_373798ea9763d3a0be5ce78f7e3f79f0._comment 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 0000000000..32056270e9 --- /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. +"""]]