close
This commit is contained in:
parent
fe5f7b9a48
commit
2845224884
1 changed files with 17 additions and 0 deletions
|
@ -20,3 +20,20 @@ or (after this fails) retrying with
|
||||||
### What version of git-annex are you using? On what operating system?
|
### What version of git-annex are you using? On what operating system?
|
||||||
|
|
||||||
I am running git 1.9.0 from git (5f95c9f850b19b368c43ae399cc831b17a26a5ac in the git git repo) on Ubuntu 13.04.
|
I am running git 1.9.0 from git (5f95c9f850b19b368c43ae399cc831b17a26a5ac in the git git repo) on Ubuntu 13.04.
|
||||||
|
|
||||||
|
> More encfs brain-damange.
|
||||||
|
|
||||||
|
One such limitation is filename length. If your underlying
|
||||||
|
filesystem limits you to N characters in a filename, then
|
||||||
|
EncFS will limit you to approximately 3*(N-2)/4.
|
||||||
|
|
||||||
|
> It's really astounding that Ubuntu inflicts that POS on users.
|
||||||
|
> However, I can't see that as justification for limiting the
|
||||||
|
> git-annex repository to filenames shorter than `PATH_MAX` -- just
|
||||||
|
> as DOS's problems with both filename length and also `:` in filenames
|
||||||
|
> is not a good reason to mangle the repository.
|
||||||
|
>
|
||||||
|
> In either case, it's up to the user to find a way to make it work.
|
||||||
|
> In the DOS case, that involves using Cygwin's git. In the encfs case,
|
||||||
|
> it presumably means checking it out into a real filesystem.
|
||||||
|
> [[done]] --[[Joey]]
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue