diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-02-19 15:54:55 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-02-19 15:54:55 -0400 |
| commit | 5126181d30be9efca43ac5164ab8b64a2c02cd09 (patch) | |
| tree | ed56c45fe2fb3d08d8794f2ad62c7c29786b6bae | |
| parent | e6188f0b27ae7d97a833ae8970210391bc25f527 (diff) | |
close
| -rw-r--r-- | doc/todo/git_annex_push.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/todo/git_annex_push.mdwn b/doc/todo/git_annex_push.mdwn index 079c83e46..4abdf253c 100644 --- a/doc/todo/git_annex_push.mdwn +++ b/doc/todo/git_annex_push.mdwn @@ -1 +1,6 @@ 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]] |