From: "Timofey Vasenin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Timofey Vasenin <timofey.vasenin@gmail.com>,
Timofey Vasenin <timofey.vasenin@gmail.com>
Subject: [PATCH] gitignore.txt: fix slash-rules example
Date: Tue, 14 May 2024 16:53:02 +0000 [thread overview]
Message-ID: <pull.1720.git.git.1715705582609.gitgitgadget@gmail.com> (raw)
From: Timofey Vasenin <timofey.vasenin@gmail.com>
Fix an apparent typo, introduced in:
1a58bad014 (gitignore.txt: make slash-rules more readable, 2019-06-04)
Reported-by: Andrey Strizhkin <astrizhkin@biarum.com>
Signed-off-by: Timofey Vasenin <timofey.vasenin@gmail.com>
---
gitignore.txt: fix slash-rules example
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1720%2Ftvasenin%2Ftvasenin%2Fgitignore-slash-rules-example-fix-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1720/tvasenin/tvasenin/gitignore-slash-rules-example-fix-v1
Pull-Request: https://github.com/git/git/pull/1720
Documentation/gitignore.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/gitignore.txt b/Documentation/gitignore.txt
index 5e0964ef419..7142fa10acc 100644
--- a/Documentation/gitignore.txt
+++ b/Documentation/gitignore.txt
@@ -100,7 +100,7 @@ PATTERN FORMAT
will only match directories, otherwise the pattern can match both
files and directories.
- - For example, a pattern `doc/frotz/` matches `doc/frotz` directory,
+ - For example, a pattern `/doc/frotz/` matches `doc/frotz` directory,
but not `a/doc/frotz` directory; however `frotz/` matches `frotz`
and `a/frotz` that is a directory (all paths are relative from
the `.gitignore` file).
base-commit: 3e4a232f6e3bd3b7dd920bb07b21cf1c8b4e1a7f
--
gitgitgadget
next reply other threads:[~2024-05-14 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 16:53 Timofey Vasenin via GitGitGadget [this message]
2024-05-14 21:50 ` [PATCH] gitignore.txt: fix slash-rules example 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=pull.1720.git.git.1715705582609.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=timofey.vasenin@gmail.com \
/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).