{"thread":{"id":"10596","subject":"[PATCH] Documentation: quote commit messages consistently.","startedAt":"2007-11-02T17:12:57Z","lastAt":"2007-11-02T17:12:57Z","messageCount":1,"participants":["Sergei Organov"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"58009","messageId":"878x5ga7vq.fsf@osv.gnss.ru","threadId":"10596","inReplyTo":null,"subject":"[PATCH] Documentation: quote commit messages consistently.","fromName":"Sergei Organov","fromEmail":"osv@javad.com","sentAt":"2007-11-02T17:12:57Z","receivedAt":"2007-11-02T17:12:57Z","isPatch":true,"sender":{"key":"osv@javad.com","avatar":null},"body":"\nDocumentation quotes commit messages 14 times with double-quotes, and 7\ntimes with single-quotes. The patch turns everything to double-quotes.\n\nA nice side effect is that documentation becomes more Windoze-friendly\nas AFAIK single quotes won't work there.\n\nSigned-off-by: Sergei Organov <osv@javad.com>\n---\n Documentation/core-tutorial.txt |    8 ++++----\n Documentation/everyday.txt      |    4 ++--\n Documentation/git-reset.txt     |    2 +-\n 3 files changed, 7 insertions(+), 7 deletions(-)\n\ndiff --git a/Documentation/core-tutorial.txt b/Documentation/core-tutorial.txt\nindex 5df97a1..99817c5 100644\n--- a/Documentation/core-tutorial.txt\n+++ b/Documentation/core-tutorial.txt\n@@ -828,7 +828,7 @@ that branch, and do some work there.\n ------------------------------------------------\n $ git checkout mybranch\n $ echo \"Work, work, work\" >>hello\n-$ git commit -m 'Some work.' -i hello\n+$ git commit -m \"Some work.\" -i hello\n ------------------------------------------------\n \n Here, we just added another line to `hello`, and we used a shorthand for\n@@ -853,7 +853,7 @@ hasn't happened in the `master` branch at all. Then do\n ------------\n $ echo \"Play, play, play\" >>hello\n $ echo \"Lots of fun\" >>example\n-$ git commit -m 'Some fun.' -i hello example\n+$ git commit -m \"Some fun.\" -i hello example\n ------------\n \n since the master branch is obviously in a much better mood.\n@@ -1607,8 +1607,8 @@ in both of them.  You could merge in 'diff-fix' first and then\n 'commit-fix' next, like this:\n \n ------------\n-$ git merge -m 'Merge fix in diff-fix' diff-fix\n-$ git merge -m 'Merge fix in commit-fix' commit-fix\n+$ git merge -m \"Merge fix in diff-fix\" diff-fix\n+$ git merge -m \"Merge fix in commit-fix\" commit-fix\n ------------\n \n Which would result in:\ndiff --git a/Documentation/everyday.txt b/Documentation/everyday.txt\nindex 08c61b1..ce7c170 100644\n--- a/Documentation/everyday.txt\n+++ b/Documentation/everyday.txt\n@@ -109,7 +109,7 @@ $ tar zxf frotz.tar.gz\n $ cd frotz\n $ git-init\n $ git add . <1>\n-$ git commit -m 'import of frotz source tree.'\n+$ git commit -m \"import of frotz source tree.\"\n $ git tag v2.43 <2>\n ------------\n +\n@@ -300,7 +300,7 @@ $ git merge topic/one topic/two && git merge hold/linus <8>\n $ git checkout maint\n $ git cherry-pick master~4 <9>\n $ compile/test\n-$ git tag -s -m 'GIT 0.99.9x' v0.99.9x <10>\n+$ git tag -s -m \"GIT 0.99.9x\" v0.99.9x <10>\n $ git fetch ko && git show-branch master maint 'tags/ko-*' <11>\n $ git push ko <12>\n $ git push ko v0.99.9x <13>\ndiff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt\nindex 15e3aca..87afa6f 100644\n--- a/Documentation/git-reset.txt\n+++ b/Documentation/git-reset.txt\n@@ -157,7 +157,7 @@ need to get to the other branch for a quick bugfix.\n ------------\n $ git checkout feature ;# you were working in \"feature\" branch and\n $ work work work       ;# got interrupted\n-$ git commit -a -m 'snapshot WIP'                 <1>\n+$ git commit -a -m \"snapshot WIP\"                 <1>\n $ git checkout master\n $ fix fix fix\n $ git commit ;# commit with real log\n-- \n1.5.3.4\n"}]}