From c0c4221ed45bd029e7fed9e41fbc6e622afec204 Mon Sep 17 00:00:00 2001 From: "https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89" Date: Tue, 16 Oct 2012 16:30:57 +0000 Subject: --- doc/todo/wishlist:_An_option_like_--git-dir.mdwn | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 doc/todo/wishlist:_An_option_like_--git-dir.mdwn (limited to 'doc/todo/wishlist:_An_option_like_--git-dir.mdwn') diff --git a/doc/todo/wishlist:_An_option_like_--git-dir.mdwn b/doc/todo/wishlist:_An_option_like_--git-dir.mdwn new file mode 100644 index 000000000..cb9d374b3 --- /dev/null +++ b/doc/todo/wishlist:_An_option_like_--git-dir.mdwn @@ -0,0 +1,3 @@ +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. -- cgit v1.2.3