{"thread":{"id":"37778","subject":"[PATCH] doc: 'git status' quote the zero (NUL) character","startedAt":"2014-10-21T22:09:50Z","lastAt":"2014-10-21T22:09:50Z","messageCount":1,"participants":["Philip Oakley"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"250952","messageId":"1413929390-1624-1-git-send-email-philipoakley@iee.org","threadId":"37778","inReplyTo":null,"subject":"[PATCH] doc: 'git status' quote the zero (NUL) character","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.org","sentAt":"2014-10-21T22:09:50Z","receivedAt":"2014-10-21T22:09:50Z","isPatch":true,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"Newer web rendering of 'git status --help --web' shows the zero in\n\"NUL (ASCII 0)\" as if it is a small 'o' character. Back-tick quote the\nzero to ensure it is displayed as a full size mono-spaced font. Also\ndisplay the \"double quote (ASCII 34)\" in the same manner.\n\nSigned-off-by: Philip Oakley <philipoakley@iee.org>\n---\n Documentation/git-status.txt | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-status.txt b/Documentation/git-status.txt\nindex 4d8d530..24390d6 100644\n--- a/Documentation/git-status.txt\n+++ b/Documentation/git-status.txt\n@@ -122,7 +122,7 @@ status code.\n The fields (including the `->`) are separated from each other by a\n single space. If a filename contains whitespace or other nonprintable\n characters, that field will be quoted in the manner of a C string\n-literal: surrounded by ASCII double quote (34) characters, and with\n+literal: surrounded by double quote (ASCII `34`) characters, and with\n interior special characters backslash-escaped.\n \n For paths with merge conflicts, `X` and `Y` show the modification\n@@ -189,7 +189,7 @@ There is also an alternate -z format recommended for machine parsing. In\n that format, the status field is the same, but some other things\n change.  First, the '\\->' is omitted from rename entries and the field\n order is reversed (e.g 'from \\-> to' becomes 'to from'). Second, a NUL\n-(ASCII 0) follows each filename, replacing space as a field separator\n+(ASCII `0`) follows each filename, replacing space as a field separator\n and the terminating newline (but a space still separates the status\n field from the first filename).  Third, filenames containing special\n characters are not specially formatted; no quoting or\n-- \n1.9.4.msysgit.0\n"}]}