From: Philip Oakley <philipoakley@iee.email>
To: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] doc: check-ignore: code-quote an exclamation mark
Date: Thu, 3 Feb 2022 10:08:46 +0000 [thread overview]
Message-ID: <a6eb7dae-f362-6027-0f96-1bb276618e5e@iee.email> (raw)
In-Reply-To: <20220203095818.1927-1-philipoakley@iee.email>
Oops finger trouble. Will send V2.
On 03/02/2022 09:58, Philip Oakley wrote:
> The plain quoted exclamation mark renders as italics in the
> Windows pdf help manual.
>
> Fix this with back-tick quoting and surrounding double quotes
> as exemplified by the gitignore.txt guide.
>
> While at it, fix the surrounding double quotes for the other
> special characters usages.
>
> Signed-off-by: Philip Oakley <philipoakley@iee.email>
> ---
>
> This formating typo was noticed while investigating gfw issue #3679
>
> Documentation/git-check-ignore.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/git-check-ignore.txt b/Documentation/git-check-ignore.txt
> index 0c3924a63d..89c7e7410c 100644
> --- a/Documentation/git-check-ignore.txt
> +++ b/Documentation/git-check-ignore.txt
> @@ -33,7 +33,7 @@ OPTIONS
> Instead of printing the paths that are excluded, for each path
> that matches an exclude pattern, print the exclude pattern
> together with the path. (Matching an exclude pattern usually
> - means the path is excluded, but if the pattern begins with '!'
> + means the path is excluded, but if the pattern begins with "`\`"
Oops !
> then it is a negated pattern and matching it means the path is
> NOT excluded.)
> +
> @@ -77,7 +77,7 @@ If `--verbose` is specified, the output is a series of lines of the form:
> <pathname> is the path of a file being queried, <pattern> is the
> matching pattern, <source> is the pattern's source file, and <linenum>
> is the line number of the pattern within that source. If the pattern
> -contained a `!` prefix or `/` suffix, it will be preserved in the
> +contained a "`!`" prefix or "`/`" suffix, it will be preserved in the
> output. <source> will be an absolute path when referring to the file
> configured by `core.excludesFile`, or relative to the repository root
> when referring to `.git/info/exclude` or a per-directory exclude file.
prev parent reply other threads:[~2022-02-03 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 9:58 [PATCH] doc: check-ignore: code-quote an exclamation mark Philip Oakley
2022-02-03 10:08 ` Philip Oakley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a6eb7dae-f362-6027-0f96-1bb276618e5e@iee.email \
--to=philipoakley@iee.email \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).