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

Browse source
This commit is contained in:
Spencer 2024-10-08 03:58:55 +00:00 committed by admin
parent 0f7ba08e95
commit cbc88a878f
1 changed files with 8 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/tips/cloning_a_repository_privately.mdwn
View file

@ -48,8 +48,14 @@ recover any files stored in it.
When the git config "remote.name.private" is set, git-annex will avoid When the git config "remote.name.private" is set, git-annex will avoid
recording anything in the git-annex branch about the remote. This is recording anything in the git-annex branch about the remote. This is
set by `git-annex initremote --private`, and could also be set for set by `git-annex initremote --private`, and could also be set for
git remotes. This could be useful, perhaps. Update this tip if you have a git remotes. This may be useful if, for example, you are trying to deduplicate content,
good way to use it. bifurcate repositories, or reinject it using a temporary annex as a staging area.
Git annex is excellent for these tasks because it naturally hashes all file content,
therefore if a 'copy' appears in one repo that should belong in another, you can drop
its content or move it to deduplicate. However, in this case, git-annex logging a relationship
between the two repos is undesirable. Especially if the repos are otherwise unrelated or
one of them is temporary (to be deleted once emptied), `remote.private` is preferrable to declaring
the repo dead and doing a `forget --drop-dead --force` operation.
## where the data is actually stored ## where the data is actually stored