aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawnpdM9F8VbtQ_H5PaPMpGSxPe_d5L1eJ6w <Rafal@web>2011-05-31 17:47:13 +0000
committerGravatar admin <admin@branchable.com>2011-05-31 17:47:13 +0000
commitc4f848d29f0ee79a8a46bd27ff141d4c62257c76 (patch)
treefa643c740cfb6d11baed49166b751a68bc665a7a
parent86c5bd0327ba1ff0d6aed8ce47031a8497a3e2fb (diff)
-rw-r--r--doc/forum/__34__git_annex_lock__34___very_slow_for_big_repo.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/forum/__34__git_annex_lock__34___very_slow_for_big_repo.mdwn b/doc/forum/__34__git_annex_lock__34___very_slow_for_big_repo.mdwn
new file mode 100644
index 000000000..8ca391684
--- /dev/null
+++ b/doc/forum/__34__git_annex_lock__34___very_slow_for_big_repo.mdwn
@@ -0,0 +1,5 @@
+I found the command "git annex lock" very slow (much slower than the initial "git annex add" with SHA1), for a not so big directory, when run in a big repo.
+It seems that each underlying git command is not fast, so I thought it would be better to run them once with all files as arguments.
+I had to stop the lock command, and ran "git checkout ." (I did not change any file), is this a correct alternative?
+
+Thanks a LOT for this software, one that I missed since a long time (but wasn't able to write)!