From 2ebcc69d638c717cb02ddb84d8bf25895c33f839 Mon Sep 17 00:00:00 2001 From: xn Date: Thu, 18 Sep 2014 19:03:30 +0000 Subject: [PATCH] Added a comment --- ..._f3aec24668c35780a033f2b035df10ee._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/forum/Move_unsynced_file_in_direct_mode/comment_2_f3aec24668c35780a033f2b035df10ee._comment diff --git a/doc/forum/Move_unsynced_file_in_direct_mode/comment_2_f3aec24668c35780a033f2b035df10ee._comment b/doc/forum/Move_unsynced_file_in_direct_mode/comment_2_f3aec24668c35780a033f2b035df10ee._comment new file mode 100644 index 0000000000..971e70cdca --- /dev/null +++ b/doc/forum/Move_unsynced_file_in_direct_mode/comment_2_f3aec24668c35780a033f2b035df10ee._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="xn" + ip="71.59.214.243" + subject="comment 2" + date="2014-09-18T19:03:30Z" + content=""" +Thanks for tracking down that bug and for clearing up my confusion about `annex.autocommit`, Joey. + +I didn't realize `annex.autocommit=true` is only used by `git annex assistant` and `git annex watch`. I thought that running `git annex sync` with `annex.autocommit=true` would also commit the change. + +A few small changes to `git-annex(1)` could clarify: + + sync [remote ...] + ... + The sync process involves first committing all local *staged* changes... + + annex.autocommit + Set to false to prevent git-annex assistant and *git-annex watch* from automatically committing changes to files in the repository. + +"""]]