diff options
| author | unqueued <unqueued@web> | 2024-04-10 12:46:53 +0000 |
|---|---|---|
| committer | admin <admin@branchable.com> | 2024-04-10 12:46:53 +0000 |
| commit | 45a3c8738c4eec4e53c6e28851b312692537b8e4 (patch) | |
| tree | bbd93723cacf792cbc6bb07fb863086d82a3b93b | |
| parent | 11a2789753ca1c19c8eb1f2b712c5177c212e040 (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/copying_annex_between_remotes_manually__63__/comment_3_875474a913d23823e3866cca27cfa3ac._comment | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/forum/copying_annex_between_remotes_manually__63__/comment_3_875474a913d23823e3866cca27cfa3ac._comment b/doc/forum/copying_annex_between_remotes_manually__63__/comment_3_875474a913d23823e3866cca27cfa3ac._comment new file mode 100644 index 0000000000..19fff278ac --- /dev/null +++ b/doc/forum/copying_annex_between_remotes_manually__63__/comment_3_875474a913d23823e3866cca27cfa3ac._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="unqueued" + avatar="http://cdn.libravatar.org/avatar/3bcbe0c9e9825637ad7efa70f458640d" + subject="comment 3" + date="2024-04-10T12:46:53Z" + content=""" +I would just clone the repo to the new machine, do `git annex init`, and then rsync the contents of `.git/annex/objects`, and then do `git annex fsck --all` to have to recheck every key it knows about. + +Alternatively, if you're concerned that there might be keys that weren't properly recorded somehow, in your new repo, after `.git/annex/objects` has been transferred, you can create an ingestion directory with a flat layout of the copied keys: + +```bash +mkdir ingest && find .git/annex/objects -type f | xargs mv ingest && git annex reinject --known ingest/* +``` + +Finally, if you just want to rebuild it from scratch, do cp with the `-cL` option. If you are on macOS, it will make a reflink copy, and follow the symlinks. Delete the target .git dir and re-create it. +"""]] |