mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2017-03-02 14:04:15 -04:00
parent 1e9e96fa40
commit e4bcfcb618
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 16 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/forum/Dealing_with_long_filenames/comment_1_373798ea9763d3a0be5ce78f7e3f79f0._comment Normal file
View file

@ -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.
"""]]