diff options
| author |  Joey Hess <id@joeyh.name> | 2014-12-01 19:14:43 -0400 |
|---|---|---|
| committer | Joey Hess <id@joeyh.name> | 2014-12-01 19:14:43 -0400 |
| commit | 51c3b49b4e294a8663bd7d7743b79f7cb87129f4 (patch) | |
| tree | 178d0671b90374837c8ae55d4bdc9932644ee0ac | |
| parent | dee083948f7d9bbea8de6ba6fb483bb9e1bcae95 (diff) | |
comment
| -rw-r--r-- | doc/forum/How_to_emulate___34__one-way_sync__34__s_in_a_direct_repo__63__/comment_1_c5226964b4b64bd47d888b5616ff970b._comment | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/forum/How_to_emulate___34__one-way_sync__34__s_in_a_direct_repo__63__/comment_1_c5226964b4b64bd47d888b5616ff970b._comment b/doc/forum/How_to_emulate___34__one-way_sync__34__s_in_a_direct_repo__63__/comment_1_c5226964b4b64bd47d888b5616ff970b._comment new file mode 100644 index 000000000..91edd264d --- /dev/null +++ b/doc/forum/How_to_emulate___34__one-way_sync__34__s_in_a_direct_repo__63__/comment_1_c5226964b4b64bd47d888b5616ff970b._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2014-12-01T23:08:56Z" + content=""" +Well, if you set `remote.foo.annex-readonly` to true, then git-annex +sync won't push changes to the remote named "foo". + +You could set that in .git/config, or you could do something like +this to set it only when running the sync: + +git -c remote.foo.annex-readonly=true annex sync + +I am not sure about a good solution for sync-all-but-deletes.sh, +although it seems like the new `git annex proxy` could perhaps +be used to build it. + +discard-all-my-changes.sh could probably be implemented using the new +`git annex proxy` command. It would be pretty unsafe though! Maybe +instead make it first commit all local changes, and then use +`git annex proxy -- git reset --hard origin/master` +"""]] |