From: Junio C Hamano <gitster@pobox•com>
To: Karsten Blees <karsten.blees@gmail•com>
Cc: Git List <git@vger•kernel.org>, Jeff King <peff@peff•net>,
Duy Nguyen <pclouds@gmail•com>
Subject: Re: [PATCH 1/2] gitignore.txt: fix documentation of "**" patterns
Date: Thu, 07 Nov 2013 10:50:41 -0800 [thread overview]
Message-ID: <xmqqeh6s59mm.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <527BC037.2000106@gmail.com> (Karsten Blees's message of "Thu, 07 Nov 2013 17:30:47 +0100")
Karsten Blees <karsten.blees@gmail•com> writes:
> "**" means bold in ASCIIDOC, so we need to escape it.
>
> Signed-off-by: Karsten Blees <blees@dcon•de>
> ---
> Documentation/gitignore.txt | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/gitignore.txt b/Documentation/gitignore.txt
> index 54e334e..f971960 100644
> --- a/Documentation/gitignore.txt
> +++ b/Documentation/gitignore.txt
> @@ -113,12 +113,12 @@ full pathname may have special meaning:
>
> - A leading "`**`" followed by a slash means match in all
> directories. For example, "`**/foo`" matches file or directory
> - "`foo`" anywhere, the same as pattern "`foo`". "**/foo/bar"
> + "`foo`" anywhere, the same as pattern "`foo`". "`**/foo/bar`"
> matches file or directory "`bar`" anywhere that is directly
> under directory "`foo`".
>
> - - A trailing "/**" matches everything inside. For example,
> - "abc/**" matches all files inside directory "abc", relative
> + - A trailing "`/**`" matches everything inside. For example,
> + "`abc/**`" matches all files inside directory "`abc`", relative
> to the location of the `.gitignore` file, with infinite depth.
All, including the quoting of `abc` that does not have anything to
do with the double-asterisk, look good; thanks.
>
> - A slash followed by two consecutive asterisks then a slash
next prev parent reply other threads:[~2013-11-07 18:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 16:30 [PATCH 0/2] Improve gitignore documentation wrt excluded directories Karsten Blees
2013-11-07 16:30 ` [PATCH 1/2] gitignore.txt: fix documentation of "**" patterns Karsten Blees
2013-11-07 18:50 ` Junio C Hamano [this message]
2013-11-07 16:31 ` [PATCH 2/2] gitignore.txt: clarify recursive nature of excluded directories Karsten Blees
2013-11-07 18:57 ` Junio C Hamano
2013-11-07 19:37 ` Junio C Hamano
2013-11-07 19:55 ` Jeff King
2013-11-07 20:27 ` Karsten Blees
2013-11-07 20:57 ` Jeff King
2013-11-07 21:36 ` Karsten Blees
2013-11-07 22:43 ` Junio C Hamano
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=xmqqeh6s59mm.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=karsten.blees@gmail$(echo .)com \
--cc=pclouds@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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