From: Bagas Sanjaya <bagasdotme@gmail.com>
To: jhatton@globalfinishing.com
Cc: git@vger.kernel.org, jeffhost@microsoft.com,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH] rev-list-options.txt: fix "not be not" typo
Date: Tue, 29 Jun 2021 13:48:04 +0700 [thread overview]
Message-ID: <20210629064803.11944-1-bagasdotme@gmail.com> (raw)
In-Reply-To: <CY4PR16MB1655C5F8225B32A2029EADE2AF039@CY4PR16MB1655.namprd16.prod.outlook.com>
Jason Hatton [1] reported typo in Documentation/rev-list-options.txt,
which is fixed by s/not be not/not be/ at line 900.
[1]:
https://lore.kernel.org/git/CY4PR16MB1655C5F8225B32A2029EADE2AF039@CY4PR16MB1655.namprd16.prod.outlook.com/
Reported-by: Jason Hatton <jhatton@globalfinishing.com>
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/rev-list-options.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt
index 5bf2a85f69..5200f18d2c 100644
--- a/Documentation/rev-list-options.txt
+++ b/Documentation/rev-list-options.txt
@@ -897,7 +897,7 @@ which are not of the requested type.
+
The form '--filter=sparse:oid=<blob-ish>' uses a sparse-checkout
specification contained in the blob (or blob-expression) '<blob-ish>'
-to omit blobs that would not be not required for a sparse checkout on
+to omit blobs that would not be required for a sparse checkout on
the requested refs.
+
The form '--filter=tree:<depth>' omits all blobs and trees whose depth
base-commit: 670b81a890388c60b7032a4f5b879f2ece8c4558
--
2.25.1
next prev parent reply other threads:[~2021-06-29 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 22:21 Documentation Typo Jason Hatton
2021-06-29 6:48 ` Bagas Sanjaya [this message]
2021-07-13 22:31 ` [PATCH] doc/rev-list-options: fix duplicate word typo Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210629064803.11944-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=jeffhost@microsoft.com \
--cc=jhatton@globalfinishing.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).