summaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/wishlist:_An_option_like_--git-dir.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/todo/wishlist:_An_option_like_--git-dir.mdwn b/doc/todo/wishlist:_An_option_like_--git-dir.mdwn
index cb9d374b3..0582d9892 100644
--- a/doc/todo/wishlist:_An_option_like_--git-dir.mdwn
+++ b/doc/todo/wishlist:_An_option_like_--git-dir.mdwn
@@ -1,3 +1,5 @@
I'm currently integrating git-annex support into a filesystem synchronization tool that I use, and I have a use case where I'd like to run "git annex sync' on a local directory, and then automatically ssh over to remote hosts and run "git annex sync" in the related annex on that remote host. However, while I can easily "cd" on the local, there is no really easy way to "cd" on the remote without a hack.
If I could say: git annex --annex-dir=PATH sync, where PATH is the annex directory, it would solve all my problems, and would also provide a nice correlation to the --git-dir option used by most Git commands. The basic idea is that I shouldn't have to be IN the directory to run git-annex commands, I should be able to tell git-annex which directory to apply its commands to.
+
+> AFAIK this is fully supported for some time, so [[done]] --[[Joey]]