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

comment

Browse source 
This commit was sponsored by Denis Dzyubenko on Patreon.
This commit is contained in:
Joey Hess 2017-01-30 14:10:08 -04:00
parent 546a5692c3
commit 67ffb8bada
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 25 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

25
doc/forum/git-annex_across_two_filesystems/comment_7_b87281c6a8b068cec60d2d5b7d015a23._comment Normal file
View file

@ -0,0 +1,25 @@
[[!comment format=mdwn
username="joey"
subject="""comment 7"""
date="2017-01-30T17:54:47Z"
content="""
Hmm, this is a rather old forum thread to be reactivating, maybe a new
thread more about your specific use case, Thomas?
Your master repository idea seems like a good one. If the master
repository is cloned with `git clone --shared` then that clone will
hard link files between it and the master repository (assuming
a git-annex rather newer than the start date of this forum thread!),
so multiple repositories will only have one copy of the file.
Of course, since it uses hard links, master and clone need to
be on the same drive.
There are probably ways to improve git-annex to handle this kind of use
case better. Maybe `git clone --shared` across filesystems should
use symlinks rather than hard links or something like that.
That might take some time to design and implement (it changes a core
invariant of git-annex, that .git/annex/objects/ contains files, not
symlinks).
Happy to discuss other options..
"""]]