git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "oneee via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: oneee <kimww0306@gmail.com>, onee-only <kimww0306@gmail.com>
Subject: [PATCH] doc: sparse-checkout: Fix list markers
Date: Mon, 21 Apr 2025 12:41:40 +0000	[thread overview]
Message-ID: <pull.1948.git.git.1745239300668.gitgitgadget@gmail.com> (raw)

From: onee-only <kimww0306@gmail.com>

Changed the list markers from a mix of "(1)" and "(b)" to a
consistent numeric format "(1)", "(2)" for clarity and consistency.

Signed-off-by: onee-only <kimww0306@gmail.com>
---
    doc: sparse-checkout: Fix list markers

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1948%2Fonee-only%2Ffix-sparse-checkout-doc-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1948/onee-only/fix-sparse-checkout-doc-v1
Pull-Request: https://github.com/git/git/pull/1948

 Documentation/technical/sparse-checkout.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/technical/sparse-checkout.adoc b/Documentation/technical/sparse-checkout.adoc
index dc2e763bbec..8202172b70b 100644
--- a/Documentation/technical/sparse-checkout.adoc
+++ b/Documentation/technical/sparse-checkout.adoc
@@ -66,7 +66,7 @@ sparsity patterns: patterns from $GIT_DIR/info/sparse-checkout used to
 	reasons: (1) users in cone mode specify directories rather than
 	patterns (their directories are transformed into patterns, but
 	users may think you are talking about non-cone mode if you use the
-	word "patterns"), and (b) the sparse specification might
+	word "patterns"), and (2) the sparse specification might
 	transiently differ in the working tree or index from the sparsity
 	patterns (see "Sparse specification vs. sparsity patterns").
 

base-commit: 4bbb303af69990ccd05fe3a2eb58a1ce036f8220
-- 
gitgitgadget

             reply	other threads:[~2025-04-21 12:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21 12:41 oneee via GitGitGadget [this message]
2025-05-28  6:56 ` [PATCH] doc: sparse-checkout: Fix list markers Kristoffer Haugsbakk
2025-05-28  7:20   ` Eric Sunshine
2025-05-28  8:01     ` Kristoffer Haugsbakk
2025-05-30  3:43       ` oneee
2025-05-30  5:00         ` Eric Sunshine
2025-05-30  7:18           ` oneee
2025-05-30 13:38           ` Junio C Hamano
2025-05-28  7:14 ` Patrick Steinhardt
2025-05-30  7:22 ` [PATCH v2] doc: sparse-checkout: use consistent inline list style oneee via GitGitGadget
2025-05-30  7:41   ` Kristoffer Haugsbakk
  -- strict thread matches above, loose matches on Subject: below --
2025-05-28  6:19 [PATCH] doc: sparse-checkout: Fix list markers oneee
2025-05-28  6:36 ` Kristoffer Haugsbakk
2025-05-28  7:14 ` Patrick Steinhardt

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.1948.git.git.1745239300668.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kimww0306@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).