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 2023-08-22 12:21:17 -04:00
parent d4ca85fd23
commit 80be770041
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 26 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

26
doc/forum/Differences_between_unlocked_and_directory_remote/comment_2_164489438245c38383645822a93cb80c._comment Normal file
View file

@ -0,0 +1,26 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2023-08-22T16:11:56Z"
content="""
The directory special remote with `importtree=yes exporttree=yes` is indeed
getting fairly close to feature parity with using all unlocked files with
`annex.thin` set.
One big difference is that such a special remote will always be untrusted.
Which might prevent dropping files from elsewhere.
Importing from the directory special remote is slower than just running
`git commit`. And it probably always will be; git is just fast.
Although importing was sped up significantly a few months ago.
Using annex.thin needs the filesystem to support hard links, or git-annex
stores 2 copies of every file. This is the main reason I'd use a directory
special remote instead sometimes, when using a filesystem like FAT.
Another reason is if there's some requirement that the directory *not* be a
git repository. Eg, if it's published by a web server, but you don't want
to publish all the git history.
Otherwise, I'd always prefer the git repository.
"""]]