mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff Hostetler <>
	Jeff Hostetler <>
Subject: [PATCH v7] fixup: rev-list-options text
Date: Thu, 14 Dec 2017 21:19:09 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

From: Jeff Hostetler <>

Signed-off-by: Jeff Hostetler <>
 Documentation/rev-list-options.txt | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt
index 8d8b7f4..b7237b9 100644
--- a/Documentation/rev-list-options.txt
+++ b/Documentation/rev-list-options.txt
@@ -714,9 +714,9 @@ ifdef::git-rev-list[]
 The form '--filter=blob:none' omits all blobs.
-The form '--filter=blob:limit=<n>[kmg]' omits blobs larger than n bytes
-or units.  n may be zero.  The suffixes k, m, and g can be used to name
-units in KiB, MiB, or GiB.  For example, 'blob:limit=1k' is the same
+The form '--filter=blob:limit=<n>[kmg]' omits blobs larger than n bytes or
+units.  '<n>' may be zero.  The suffixes 'k', 'm', and 'g' can be used to
+name units in KiB, MiB, or GiB.  For example, 'blob:limit=1k' is the same
 as 'blob:limit=1024'.
 The form '--filter=sparse:oid=<blob-ish>' uses a sparse-checkout
@@ -725,7 +725,7 @@ to omit blobs that would not be not required for a sparse checkout on
 the requested refs.
 The form '--filter=sparse:path=<path>' similarly uses a sparse-checkout
-specification contained in <path>.
+specification contained in '<path>'.
 	Turn off any previous `--filter=` argument.

  reply	other threads:[~2017-12-14 21:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 21:19 [PATCH v7] Partial clone part 1: object filtering Jeff Hostetler
2017-12-14 21:19 ` Jeff Hostetler [this message]
2017-12-14 21:36   ` [PATCH v7] fixup: rev-list-options text Christian Couder

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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

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).