summaryrefslogtreecommitdiff
path: root/doc/upgrades
diff options
context:
space:
mode:
authorGravatar anarcat <anarcat@web>2014-09-18 22:27:46 +0000
committerGravatar admin <admin@branchable.com>2014-09-18 22:27:46 +0000
commit78bef2bbb873fa41de277092d9c897fa8d6ee923 (patch)
treeeb16b703e4466a06cb96b1e7026a8c23e9a1add6 /doc/upgrades
parent9ed1b0799e77d7de4720cbb3c092aa006afba8c0 (diff)
git history is hard to kill, make sure it's clear
Diffstat (limited to 'doc/upgrades')
-rw-r--r--doc/upgrades/insecure_embedded_creds.mdwn5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/upgrades/insecure_embedded_creds.mdwn b/doc/upgrades/insecure_embedded_creds.mdwn
index 117ee96a4..19713f9b0 100644
--- a/doc/upgrades/insecure_embedded_creds.mdwn
+++ b/doc/upgrades/insecure_embedded_creds.mdwn
@@ -26,8 +26,9 @@ to deal with it:
and running `git annex enableremote $remotename embedcreds=yes`
2. Remove the history of the git-annex branch of the repository.
- You can use `git annex forget`` to do that; note that it will
- remove other historical data too.
+ You can use `git annex forget` to do that; note that it will
+ remove other historical data too. Keep in mind that this will not
+ necessarily delete data from clones you do not control.
3. If you're the only one who has access to the repository, you could decide
to leave it as-is. It's no more insecure than if you had used