diff options
author | 2014-05-26 19:47:41 +0000 | |
---|---|---|
committer | 2014-05-26 19:47:41 +0000 | |
commit | 579808e51c0c10efc92fd0e0ea43b4963d8cfe8b (patch) | |
tree | 4fd5e8996eea3ecd58310c99599f541610f9fe19 /doc | |
parent | c03193814ccbbd329dc8515b095e4686364965ee (diff) |
New post
Diffstat (limited to 'doc')
-rw-r--r-- | doc/forum/Manual_commit_message_in_direct_mode.mdwn | 3 |
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? |