diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2013-12-16 17:04:56 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-12-16 17:04:56 +0000 |
| commit | cd0889cf5ef37ff6c38af6704b4db85914f24892 (patch) | |
| tree | 467d0ebae57e6bdaad0d9312c1d531a8990d3146 /doc/tips | |
| parent | 6a2559cc246e10b1aa43f8f95bcb5273e20a29de (diff) | |
Added a comment
Diffstat (limited to 'doc/tips')
| -rw-r--r-- | doc/tips/what_to_do_when_you_lose_a_repository/comment_4_679eb9be0bfb9d48a2b96383c4816f62._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/tips/what_to_do_when_you_lose_a_repository/comment_4_679eb9be0bfb9d48a2b96383c4816f62._comment b/doc/tips/what_to_do_when_you_lose_a_repository/comment_4_679eb9be0bfb9d48a2b96383c4816f62._comment new file mode 100644 index 000000000..e0aa916a6 --- /dev/null +++ b/doc/tips/what_to_do_when_you_lose_a_repository/comment_4_679eb9be0bfb9d48a2b96383c4816f62._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.87" + subject="comment 4" + date="2013-12-16T17:04:44Z" + content=""" +I wouldn't recommend running `git annex forget --drop-dead` right after losing a drive. You might find the drive again, or get the dead drive to work again. Even if you know you'll never find it, you may want to query git-annex to find files that were only located on that drive, and deal with them, etc. + +But if you're worried about that information in the git-annex branch cluttering up the git repository, you keep in mind that `git annex forget` will let you remove it at some point in the future. +"""]] |