diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-07-31 16:56:56 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-07-31 16:56:56 -0400 |
| commit | d4aa37352d19e84cc1a9574fcef1c62b0b4ae4c7 (patch) | |
| tree | 70d95ae5b8fe97bb5493cd7be17ad0316f867af4 | |
| parent | 1b21848081be755527237fdacdceecf00115da11 (diff) | |
| parent | 8ecf3918cf4d342821bf4b0afeaa6577a125d560 (diff) | |
Merge branch 'master' of ssh://git-annex.branchable.com
| -rw-r--r-- | doc/todo/git_annex_push.mdwn | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/todo/git_annex_push.mdwn b/doc/todo/git_annex_push.mdwn new file mode 100644 index 000000000..079c83e46 --- /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) |