{"thread":{"id":"57361","subject":"[PATCH] doc: check-ignore: code-quote an exclamation mark","startedAt":"2022-02-03T09:58:30Z","lastAt":"2022-02-03T10:08:51Z","messageCount":2,"participants":["Philip Oakley"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"447597","messageId":"20220203095818.1927-1-philipoakley@iee.email","threadId":"57361","inReplyTo":null,"subject":"[PATCH] doc: check-ignore: code-quote an exclamation mark","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.email","sentAt":"2022-02-03T09:58:18Z","receivedAt":"2022-02-03T09:58:30Z","isPatch":true,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"The plain quoted exclamation mark renders as italics in the\nWindows pdf help manual.\n\nFix this with back-tick quoting and surrounding double quotes\nas exemplified by the gitignore.txt guide.\n\nWhile at it, fix  the surrounding double quotes for the other\nspecial characters usages.\n\nSigned-off-by: Philip Oakley <philipoakley@iee.email>\n---\n\nThis formating typo was noticed while investigating gfw issue #3679\n\n Documentation/git-check-ignore.txt | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-check-ignore.txt b/Documentation/git-check-ignore.txt\nindex 0c3924a63d..89c7e7410c 100644\n--- a/Documentation/git-check-ignore.txt\n+++ b/Documentation/git-check-ignore.txt\n@@ -33,7 +33,7 @@ OPTIONS\n \tInstead of printing the paths that are excluded, for each path\n \tthat matches an exclude pattern, print the exclude pattern\n \ttogether with the path.  (Matching an exclude pattern usually\n-\tmeans the path is excluded, but if the pattern begins with '!'\n+\tmeans the path is excluded, but if the pattern begins with \"`\\`\"\n \tthen it is a negated pattern and matching it means the path is\n \tNOT excluded.)\n +\n@@ -77,7 +77,7 @@ If `--verbose` is specified, the output is a series of lines of the form:\n <pathname> is the path of a file being queried, <pattern> is the\n matching pattern, <source> is the pattern's source file, and <linenum>\n is the line number of the pattern within that source.  If the pattern\n-contained a `!` prefix or `/` suffix, it will be preserved in the\n+contained a \"`!`\" prefix or \"`/`\" suffix, it will be preserved in the\n output.  <source> will be an absolute path when referring to the file\n configured by `core.excludesFile`, or relative to the repository root\n when referring to `.git/info/exclude` or a per-directory exclude file.\n-- \n2.35.1.windows.2\n\n"},{"id":"447599","messageId":"a6eb7dae-f362-6027-0f96-1bb276618e5e@iee.email","threadId":"57361","inReplyTo":"20220203095818.1927-1-philipoakley@iee.email","subject":"Re: [PATCH] doc: check-ignore: code-quote an exclamation mark","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.email","sentAt":"2022-02-03T10:08:46Z","receivedAt":"2022-02-03T10:08:51Z","isPatch":true,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"Oops finger trouble.  Will send V2.\n\nOn 03/02/2022 09:58, Philip Oakley wrote:\n> The plain quoted exclamation mark renders as italics in the\n> Windows pdf help manual.\n>\n> Fix this with back-tick quoting and surrounding double quotes\n> as exemplified by the gitignore.txt guide.\n>\n> While at it, fix  the surrounding double quotes for the other\n> special characters usages.\n>\n> Signed-off-by: Philip Oakley <philipoakley@iee.email>\n> ---\n>\n> This formating typo was noticed while investigating gfw issue #3679\n>\n>  Documentation/git-check-ignore.txt | 4 ++--\n>  1 file changed, 2 insertions(+), 2 deletions(-)\n>\n> diff --git a/Documentation/git-check-ignore.txt b/Documentation/git-check-ignore.txt\n> index 0c3924a63d..89c7e7410c 100644\n> --- a/Documentation/git-check-ignore.txt\n> +++ b/Documentation/git-check-ignore.txt\n> @@ -33,7 +33,7 @@ OPTIONS\n>  \tInstead of printing the paths that are excluded, for each path\n>  \tthat matches an exclude pattern, print the exclude pattern\n>  \ttogether with the path.  (Matching an exclude pattern usually\n> -\tmeans the path is excluded, but if the pattern begins with '!'\n> +\tmeans the path is excluded, but if the pattern begins with \"`\\`\"\nOops !\n>  \tthen it is a negated pattern and matching it means the path is\n>  \tNOT excluded.)\n>  +\n> @@ -77,7 +77,7 @@ If `--verbose` is specified, the output is a series of lines of the form:\n>  <pathname> is the path of a file being queried, <pattern> is the\n>  matching pattern, <source> is the pattern's source file, and <linenum>\n>  is the line number of the pattern within that source.  If the pattern\n> -contained a `!` prefix or `/` suffix, it will be preserved in the\n> +contained a \"`!`\" prefix or \"`/`\" suffix, it will be preserved in the\n>  output.  <source> will be an absolute path when referring to the file\n>  configured by `core.excludesFile`, or relative to the repository root\n>  when referring to `.git/info/exclude` or a per-directory exclude file.\n\n"}]}