From a765316b595e8666c8de7f5eb74ab58728f5bf8d Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 27 May 2014 16:10:29 +0000 Subject: Added a comment --- .../comment_1_32f95eefec25bb127ed96248446c21b1._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Manual_commit_message_in_direct_mode/comment_1_32f95eefec25bb127ed96248446c21b1._comment diff --git a/doc/forum/Manual_commit_message_in_direct_mode/comment_1_32f95eefec25bb127ed96248446c21b1._comment b/doc/forum/Manual_commit_message_in_direct_mode/comment_1_32f95eefec25bb127ed96248446c21b1._comment new file mode 100644 index 000000000..bb53d4458 --- /dev/null +++ b/doc/forum/Manual_commit_message_in_direct_mode/comment_1_32f95eefec25bb127ed96248446c21b1._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.176" + subject="comment 1" + date="2014-05-27T16:10:29Z" + content=""" +Yes, you can use the `-c core.bare=false` trick to bypass the direct mode guard if you want to. Just bear in mind that it's very easy to shoot yourself in the foot by passing -a or filenames to git commit, which then checks the whole large file into git.. +"""]] -- cgit v1.2.3