From 1d51542cd45ce10c6c9a1b2293bb0d6255ec257c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 4 Aug 2015 16:23:21 -0400 Subject: [PATCH] comment --- ..._54c5494ec21621298b3111cd7c2325b1._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/todo/git_annex_push/comment_1_54c5494ec21621298b3111cd7c2325b1._comment diff --git a/doc/todo/git_annex_push/comment_1_54c5494ec21621298b3111cd7c2325b1._comment b/doc/todo/git_annex_push/comment_1_54c5494ec21621298b3111cd7c2325b1._comment new file mode 100644 index 0000000000..608f1f9368 --- /dev/null +++ b/doc/todo/git_annex_push/comment_1_54c5494ec21621298b3111cd7c2325b1._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-08-04T20:19:22Z" + content=""" +`git annex sync --content` does what you want, only it also does a pull and +a merge from remotes. + +I don't know that wanting to only push, w/o pull and merge, is common +enough to make a separate command for it. + +There's also the problem that to push the git-annex branch, it really +makes sense to first pull/merge from the remote. Otherwise, the push +is not likely to work as well. And too, it makes sense to update the +git-annex branch from remotes in order to know what files that have, so +that info can be better used to decide which files to send to them -- +especially when preferred content might make some file not be sent to all +remotes, depending on which other remotes contain the file. +"""]]