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

add a warning and a related todo

Browse source 
arising from a conversation at FOSSY
This commit is contained in:
Joey Hess 2023-07-13 19:57:34 -04:00
parent ff118cdfe8
commit 0df94132d9
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
doc/tips/splitting_a_repository.mdwn
View file

@ -70,6 +70,9 @@ Finally the annexed file contents need to be copied to the new repository:
# Fix up annex links to content and make sure it's all ok.
git annex fsck
Warning: This method of copying the annexed file contents and dropping
the unused ones causes the git-annex branch to log information.
# alternative older method
Here is another way to do it. Suppose the old big repo is at `~/oldrepo`:

14
doc/todo/filter-branch_for_objects.mdwn Normal file
View file

@ -0,0 +1,14 @@
`git-annex filter-branch` can be used to split a git-annex repository.
However, the approach in [[tips/splitting_a_repository]] then copies all
objects into the new repository and drops unused objects. And dropunused
updates location log in that situation, even when the location log didn't
exist in that repository before. So, that approach leaks information about
objects that were in the original repository into the split repository.
Splitting a git-annex repository is something that, when you need to do it,
you may have good reasons to want to avoid any such leakage of
information.
So perhaps add a feature that copies only the needed objects over to the
split repository? Or update the tip with a better method that avoids this
problem. --[[Joey]]