summaryrefslogtreecommitdiff
path: root/doc/bugs/ordering.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-01-31 16:06:27 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-01-31 16:06:27 -0400
commit9fe5865a07ac5a66c7ecaad4a5682b205939735d (patch)
tree489ea57bb9e3421de75b49d0fbd4e5095cfaf8af /doc/bugs/ordering.mdwn
parentd007e58a5437daa72062453fc6f44c5beb7d271d (diff)
annoyance
Diffstat (limited to 'doc/bugs/ordering.mdwn')
-rw-r--r--doc/bugs/ordering.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/ordering.mdwn b/doc/bugs/ordering.mdwn
new file mode 100644
index 000000000..902cf7676
--- /dev/null
+++ b/doc/bugs/ordering.mdwn
@@ -0,0 +1,10 @@
+One would expect "git annex get foo bar" to first retrieve foo, and then
+bar. Actually though, it will operate on them in alphabetical order
+(probably). This is annoying when you wanted to 1st list the most important
+files to get. Maybe you'll run out of time before all can be gotten. The
+workaround of course is to run "git annex get" twice.
+
+This ordering comes from "git ls-files". git-annex passes it all the files
+the user specified. This is a useful optimisation -- earlier it would
+run "git ls-files" once per parameter, and so "git annex get *" could be
+rather slow. But, it produces this ordering problem.