summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar xn <xn@web>2014-09-18 19:03:30 +0000
committerGravatar admin <admin@branchable.com>2014-09-18 19:03:30 +0000
commit21e3bf54bcef893026624cf68a0947d47f450358 (patch)
tree5ef56b0f6f74010c9c9648ba7015244bbb84bcc6
parent4e7bfb92c467fd63ee6884d0f4b611916794c6dc (diff)
Added a comment
-rw-r--r--doc/forum/Move_unsynced_file_in_direct_mode/comment_2_f3aec24668c35780a033f2b035df10ee._comment20
1 files changed, 20 insertions, 0 deletions
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 000000000..971e70cdc
--- /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.
+
+"""]]