From c0093fb8a739e17d9a53e9bec1660f707c21faaa Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnxvt4mc32O0ctvPGhhII_ZKsHUiaD2o7I" Date: Wed, 28 May 2014 04:40:27 +0000 Subject: [PATCH] Added a comment --- ...comment_2_bf1d10067379c802ac5020d8becd6d35._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Manual_commit_message_in_direct_mode/comment_2_bf1d10067379c802ac5020d8becd6d35._comment diff --git a/doc/forum/Manual_commit_message_in_direct_mode/comment_2_bf1d10067379c802ac5020d8becd6d35._comment b/doc/forum/Manual_commit_message_in_direct_mode/comment_2_bf1d10067379c802ac5020d8becd6d35._comment new file mode 100644 index 0000000000..facb5ce334 --- /dev/null +++ b/doc/forum/Manual_commit_message_in_direct_mode/comment_2_bf1d10067379c802ac5020d8becd6d35._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnxvt4mc32O0ctvPGhhII_ZKsHUiaD2o7I" + nickname="William" + subject="comment 2" + date="2014-05-28T04:40:27Z" + content=""" +Joey, thanks for clarifying that. I learned about the perils of using regular git commands in direct mode before the guard was implemented, so I will use with care. Specifying a commit message is really the only case where I am tempted to bypass the the `git annex` subcommands in direct mode. + + +"""]]