diff options
| author |  pete.ward@26c41318616c4cf9601d0431557c1df734ccdb77 <peteward@web> | 2015-12-16 22:15:17 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-12-16 22:15:17 +0000 |
| commit | bec325d984ae2df767cd798e431bae445e97f773 (patch) | |
| tree | 062a78324bfaf30e8d450ba06efda96305f15512 | |
| parent | 4136fadd940b5996464fc175ccd3b0ad3788e259 (diff) | |
| -rw-r--r-- | doc/forum/All_repos_on_same_filesystem.mdwn | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/forum/All_repos_on_same_filesystem.mdwn b/doc/forum/All_repos_on_same_filesystem.mdwn new file mode 100644 index 000000000..ee61ab725 --- /dev/null +++ b/doc/forum/All_repos_on_same_filesystem.mdwn @@ -0,0 +1,14 @@ +Hi, + I am looking to find out the best way to use git annex, when all repos will live on the same filesystem, using a central repo. + +What I have so far is, after creating the main repo (mainrepo). + +Create clones via: git clone -shared mainrepo clonerepo + +Then use "git annex add" and "git add". When it comes to making the data accessible to the mainrepo, it is a little unclear to me. +There is a lot of disjoint information regarding pull/pushing content and which directions use hardlinks vs copies etc. So I +was hoping that someone could fill me in on best practices. + +Thanks in advance! + +Pete |