diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-10-12 13:34:43 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-10-12 13:34:43 -0400 |
| commit | 81b5923ff2fe7487d92491fffdd5c88e3de79eca (patch) | |
| tree | 4de524bc3d9a186c71a9d56b3c47d13782e2d926 | |
| parent | e9427fac4656f92429177903242b143697c5e4fa (diff) | |
already done
| -rw-r--r-- | doc/todo/whishlist:_temporary_relinking_to_remotes.mdwn | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/todo/whishlist:_temporary_relinking_to_remotes.mdwn b/doc/todo/whishlist:_temporary_relinking_to_remotes.mdwn index 1c0c55fa9..3b1ca70eb 100644 --- a/doc/todo/whishlist:_temporary_relinking_to_remotes.mdwn +++ b/doc/todo/whishlist:_temporary_relinking_to_remotes.mdwn @@ -17,3 +17,14 @@ I know that many specialremotes will not support this without much hassle, but i To keep the data consistent there can be a constraint that every action (add, sync, commit or others) first issue a `resetlinks`. What do you think of that? + +> Already implemented via the `annex.hardlink` configuration. +> +> I don't think that separate commands/options to control whether or not +> to hard link makes sense, because a repository containing hardlinks +> needs to be set as untrusted to avoid breaking numcopies counting. +> Which is done automatically by git-annex when it detects the repository +> was cloned with `git clone --shared`. +> +> [[done]] +> --[[Joey]] |