aboutsummaryrefslogtreecommitdiff
path: root/doc/todo/git_annex_push.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/todo/git_annex_push.mdwn')
-rw-r--r--doc/todo/git_annex_push.mdwn6
1 files changed, 0 insertions, 6 deletions
diff --git a/doc/todo/git_annex_push.mdwn b/doc/todo/git_annex_push.mdwn
deleted file mode 100644
index 4abdf253c..000000000
--- a/doc/todo/git_annex_push.mdwn
+++ /dev/null
@@ -1,6 +0,0 @@
-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)
-
-> After this was opened, some options were added, so use:
-> `git-annex sync --no-pull --content`
->
-> [[done]] --[[Joey]]