summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://christian.amsuess.com/chrysn <chrysn@web>2011-06-14 17:01:13 +0000
committerGravatar admin <admin@branchable.com>2011-06-14 17:01:13 +0000
commitf4609a5d288525abbb47e361194601d21684df8e (patch)
treefa3dd0163e5223d8dca8e874dce81af2f6f45f93
parentf547277b751d81f516a638bc281735fa1946b17d (diff)
minor bug report
-rw-r--r--doc/bugs/git_annex_initremote_walks_.git-annex.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_initremote_walks_.git-annex.mdwn b/doc/bugs/git_annex_initremote_walks_.git-annex.mdwn
new file mode 100644
index 000000000..6e3a60e3b
--- /dev/null
+++ b/doc/bugs/git_annex_initremote_walks_.git-annex.mdwn
@@ -0,0 +1,10 @@
+a [[!taglink minor]] <!-- (a suggestion for introducing severity tags on bugs,
+feel free to discard) --> issue: `git annex initremote` (in particular, adding
+a key as described in [[encryption]] -- `git annex initremote my_remote
+encryption=my_key`) seems to iterate over the `.git-annex/???/???/*.log` files
+with lstat (tested using strace).
+
+in a 50k key git-annex on a slow disk, this takes quite a while, while not
+seeming necessary (it's just re-encrypting the shared secret, is it?).
+
+could you verify the observed behavior?