From: Bagas Sanjaya <bagasdotme@gmail.com>
To: git@vger.kernel.org
Cc: "Taylor Blau" <me@ttaylorr.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Bagas Sanjaya" <bagasdotme@gmail.com>
Subject: [PATCH] repack: Sync list of options between synopsis and description in the documentation
Date: Wed, 9 Mar 2022 19:34:47 +0700 [thread overview]
Message-ID: <20220309123447.852883-1-bagasdotme@gmail.com> (raw)
Options list in the synopsis and description section of git-repack(1)
are out of sync. The latest addition was in commit 1d89d88d37
(builtin/repack.c: support writing a MIDX while repacking, 2021-09-28),
which only adds -m/--write-midx option.
Add missing options to the synopsis. Additionaly, sort according to the
order they appear in the description.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/git-repack.txt | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-repack.txt b/Documentation/git-repack.txt
index ee30edc178..26e997bde1 100644
--- a/Documentation/git-repack.txt
+++ b/Documentation/git-repack.txt
@@ -9,7 +9,13 @@ git-repack - Pack unpacked objects in a repository
SYNOPSIS
--------
[verse]
-'git repack' [-a] [-A] [-d] [-f] [-F] [-l] [-n] [-q] [-b] [-m] [--window=<n>] [--depth=<n>] [--threads=<n>] [--keep-pack=<pack-name>] [--write-midx]
+'git repack' [-a] [-A] [-d] [-l] [-f] [-F] [-q | --quiet] [-n] [--window=<n>]
+ [--depth=<n>] [--threads=<n>] [--window-memory=<n>]
+ [--max-pack-size=<n>] [-b | --write-bitmap-index]
+ [--pack-kept-objects] [--keep-pack=<pack-name>]
+ [--unpack-unreachable=<when>] [-k | --keep-unreachable]
+ [-i | --delta-islands] [-g | --geometric <factor>]
+ [-m | --write-midx]
DESCRIPTION
-----------
base-commit: c2162907e9aa884bdb70208389cb99b181620d51
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2022-03-09 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 12:34 Bagas Sanjaya [this message]
2022-03-09 13:17 ` [PATCH] repack: Sync list of options between synopsis and description in the documentation Shaoxuan Yuan
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=20220309123447.852883-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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).