From 8d19f7f09e932bef7660a73378d1c6f78bc51968 Mon Sep 17 00:00:00 2001 From: Atemu Date: Sat, 22 Feb 2025 10:48:23 +0000 Subject: [PATCH 1/3] --- .../Move_part_of_one_repository_into_other.mdwn | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/Move_part_of_one_repository_into_other.mdwn diff --git a/doc/forum/Move_part_of_one_repository_into_other.mdwn b/doc/forum/Move_part_of_one_repository_into_other.mdwn new file mode 100644 index 0000000000..036b76a5ef --- /dev/null +++ b/doc/forum/Move_part_of_one_repository_into_other.mdwn @@ -0,0 +1,15 @@ +I have two sets of git annex repositories: + +A: Contains a tree of some files and then a *huge* chunk of files +B: Contains already has a ton of files + +Both repository sets have their own set of repos on different machines that are connected to another. + +I now want the huge chunk of content in A to be in B instead of A but the rest of the content should remain in A. + +On git side, I think basically what this boils down to is that I want to move the git sub-tree to the other repo which ought to be possible by simply `git add`ing them. I might want to get fancy and cherry-pick the commit from the other repo in a way that keeps it but moves the content to another subdirectory but that's the simple part. + +On the git-annex side, I want all the keys that were exclusively referenced in this set of files to be marked as dead and dropped from remotes which contain them. I effectively want to remove those keys from git-annex' consideration. +The keys should be added to B. They should start out with a blank location tracking state as B should not know about A's repositories. They should however retain any other metadata they previously had in A. + +How could I achieve this? From 958e9068e32499dff8f84fa31b6d9da245fdba2e Mon Sep 17 00:00:00 2001 From: Atemu Date: Sat, 22 Feb 2025 10:50:55 +0000 Subject: [PATCH 2/3] --- doc/forum/Move_part_of_one_repository_into_other.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/Move_part_of_one_repository_into_other.mdwn b/doc/forum/Move_part_of_one_repository_into_other.mdwn index 036b76a5ef..7727e1b949 100644 --- a/doc/forum/Move_part_of_one_repository_into_other.mdwn +++ b/doc/forum/Move_part_of_one_repository_into_other.mdwn @@ -1,6 +1,6 @@ I have two sets of git annex repositories: -A: Contains a tree of some files and then a *huge* chunk of files +A: Contains a tree of some files and then a *huge* chunk of files B: Contains already has a ton of files Both repository sets have their own set of repos on different machines that are connected to another. From aa2fbf552b103a42a4dfc754c33539e37adf8061 Mon Sep 17 00:00:00 2001 From: Atemu Date: Sat, 22 Feb 2025 10:51:45 +0000 Subject: [PATCH 3/3] --- doc/forum/Move_part_of_one_repository_into_other.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/Move_part_of_one_repository_into_other.mdwn b/doc/forum/Move_part_of_one_repository_into_other.mdwn index 7727e1b949..94adad499e 100644 --- a/doc/forum/Move_part_of_one_repository_into_other.mdwn +++ b/doc/forum/Move_part_of_one_repository_into_other.mdwn @@ -1,7 +1,7 @@ I have two sets of git annex repositories: A: Contains a tree of some files and then a *huge* chunk of files -B: Contains already has a ton of files +B: Already contains a ton of files Both repository sets have their own set of repos on different machines that are connected to another.