From 02ebc79ee7349b5d079e8e761082fc856126f767 Mon Sep 17 00:00:00 2001 From: "https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" Date: Fri, 31 Jul 2015 16:16:02 +0000 Subject: [PATCH] --- doc/todo/git_annex_push.mdwn | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/todo/git_annex_push.mdwn diff --git a/doc/todo/git_annex_push.mdwn b/doc/todo/git_annex_push.mdwn new file mode 100644 index 0000000000..079c83e465 --- /dev/null +++ b/doc/todo/git_annex_push.mdwn @@ -0,0 +1 @@ +A common use case for me is to use annex as really just an addition to git to store additional content. What I am ending up with is two stage procedure to submit my changes to our shared repository: git push REMOTE; git annex copy --to=REMOTE . IMHO it would only be logical if there was "git annex push REMOTE [GITPUSHOPTIONS]" which would be merely an alias for "git push REMOTE [GITPUSHOPTIONS]; git annex copy --to=REMOTE" but which will make use of annex for such common usecase simple(r)