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

removed

Browse source
This commit is contained in:
https://launchpad.net/~stephane-gourichon-lpad 2017-07-18 11:49:50 +00:00 committed by admin
parent bdc87ffe20
commit 6c4a7941ed
1 changed files with 0 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
doc/tuning/comment_3_7ffb2734b8a6c8fe6b1aa01d48ef6d10._comment
View file

@ -1,14 +0,0 @@
[[!comment format=mdwn
username="https://launchpad.net/~stephane-gourichon-lpad"
nickname="stephane-gourichon-lpad"
avatar="http://cdn.libravatar.org/avatar/02d4a0af59175f9123720b4481d55a769ba954e20f6dd9b2792217d9fa0c6089"
subject="Syncing between untuned and tuned repo?"
date="2017-07-18T11:25:42Z"
content="""
> Also, it's not safe to merge two separate git repositories that have been tuned differently (or one tuned and the other one not). git-annex will prevent merging their git-annex branches together, but it cannot prevent git merge remote/master merging two branches, and the result will be ugly at best (git annex fix can fix up the mess somewhat).
I'm highly interested in the lowercase option since current behavior has lead to a number of file duplications that are still not solved. My main use repo is 1.7TB large and holds 172.000+ annexed files and I'm definitely not the only one with a big repo.
Does migrating to a tuned repository mean unannexing everything and reimporting into a newly created annex, replica by replica then sync again? That's a high price in some setup. Or is there a way to somehow `git annex sync` between a newly created repo and an old, untuned one?
"""]]