From f10cc07577ab21f8a782247880844a9f320d2028 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnxvt4mc32O0ctvPGhhII_ZKsHUiaD2o7I" Date: Mon, 26 May 2014 19:47:41 +0000 Subject: [PATCH] New post --- doc/forum/Manual_commit_message_in_direct_mode.mdwn | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 doc/forum/Manual_commit_message_in_direct_mode.mdwn 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 0000000000..d74c366073 --- /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?