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

PATH_MAX

Browse source
This commit is contained in:
Joey Hess 2024-05-22 04:26:36 -04:00
parent 5fb307f1c5
commit 4131e31f5c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/todo/deal_with_git_fsck_symlinkPointsToGitDir.mdwn
View file

@ -24,3 +24,19 @@ configs.
Is it at all common to set `git config fetch.fsckObjects true` or
`git config receive.fsckObjects` true?
----
There is also potential breakage from git fsck now warning about symlink
targets that exceed `PATH_MAX`. On Windows, that is 260. A SHA512 key has a
symlink target of at least length 306. And even shorter keys, when located
in deep subdirectories, can have longer symlink targets than that. So
pushing to a bare repo on Windows could fail, for example. It even seems
likely this could affect pushing to Freebsd in some cases, since its
`PATH_MAX` is 1024 to Linux's 4096.
If git-annex wanted to also avoid this breakage, it could set:
git config fsck.symlinkTargetLength ignore
git config receive.fsck.symlinkTargetLength ignore
git config fetch.fsck.symlinkTargetLength ignore