From 21acb6d7b3a91693ee08ba92107308f2135bcbe4 Mon Sep 17 00:00:00 2001 From: "tamar.matsuzawa@f52849aed85183d86548fe9658bf02ed250820e6" Date: Fri, 29 May 2015 00:58:46 +0000 Subject: [PATCH] --- ..._multiple_repositories_on_one_machine.mdwn | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 doc/forum/share_.git__47__annex__47__objects_across_multiple_repositories_on_one_machine.mdwn diff --git a/doc/forum/share_.git__47__annex__47__objects_across_multiple_repositories_on_one_machine.mdwn b/doc/forum/share_.git__47__annex__47__objects_across_multiple_repositories_on_one_machine.mdwn new file mode 100644 index 0000000000..faf8f4d237 --- /dev/null +++ b/doc/forum/share_.git__47__annex__47__objects_across_multiple_repositories_on_one_machine.mdwn @@ -0,0 +1,28 @@ +Hello, + +git-annex looks very interesting and I would like it to version large binary artifacts for testing in our source code repository. + +My question: + +I want to have/can have multiple clones of the same repository on the same machine. +However, as the binary files can be huge, I would like to store the files only exactly ONCE per machine and not again in the .git/annex/objects folder of each similar cloned repository. + +To achieve that, I first created in + + /tmp/repo-clone1/.git/annex/objects + +and then symlinked + + ln -s /tmp/repo-clone1/.git/annex/objects /tmp/repo-clone2/.git/annex/objects + +such that + + /tmp/repo-clone1 + /tmp/repo-clone2 + +share the same big files and the big files are only once on the machine. + +Is this a good idea? Is there a better way to achieve this? Looks a bit hacky. Would be nicer if you can specify a dedicated "objects" folder from the start?! + +Thanks and Regards, +J