summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-05-26 18:01:48 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-05-26 18:01:48 -0400
commit95156e27bae23a3439f34e1a0426d507e0fcc58e (patch)
treea089e765dec3640622cbc9bfcdd2f45c0ad348e0
parent357c16ba9898e013345a0d56202a0cf3ba63b008 (diff)
parent579808e51c0c10efc92fd0e0ea43b4963d8cfe8b (diff)
Merge branch 'master' of ssh://git-annex.branchable.com
-rw-r--r--doc/forum/Manual_commit_message_in_direct_mode.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/Manual_commit_message_in_direct_mode.mdwn b/doc/forum/Manual_commit_message_in_direct_mode.mdwn
new file mode 100644
index 000000000..d74c36607
--- /dev/null
+++ b/doc/forum/Manual_commit_message_in_direct_mode.mdwn
@@ -0,0 +1,3 @@
+I am just returning to git-annex after some time. The last time I was using it, the [[/todo/direct_mode_guard]] was not yet in place, and I could supply my own commit messages even in a direct mode repository using `git commit`. Now that the guard is in place, is there a built-in way to provide a commit message that will be used instead of "git-annex automatic sync" by `git annex sync`?
+
+I have tried doing a manual commit with `git --git-dir=/path/to/local/.git --work-tree=/path/to/local -c core.bare=false commit -m 'Manual Commit Message'`, and it seems to work. Does this do the same thing as the part of `git annex sync` that commits any outstanding changes before syncing with remotes?