From: Nikolai Weibull <mailing-lists.git@rawuncut.elitemail.org>
To: git <git@vger.kernel.org>
Cc: Nikolai Weibull <nikolai@bitwi.se>
Subject: [PATCH 1/3] Document the -n command-line option to git-unpack-objects
Date: Tue, 15 Nov 2005 00:20:01 +0100 [thread overview]
Message-ID: <11320104011582-git-send-email-mailing-lists.git@rawuncut.elitemail.org> (raw)
In-Reply-To: <11320104011696-git-send-email-mailing-lists.git@rawuncut.elitemail.org>
This patch documents the -n command-line option to git-unpack-objects,
as it was previously undocumented.
Signed-off-by: Nikolai Weibull <nikolai@bitwi.se>
---
Documentation/git-unpack-objects.txt | 6 +++++-
unpack-objects.c | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
applies-to: 963d67921d6f65c08d51a8c93811f03274c34703
0d2b0b51463fe0fed667a7169b94d7ee52677e69
diff --git a/Documentation/git-unpack-objects.txt b/Documentation/git-unpack-objects.txt
index b716ba1..31ea34d 100644
--- a/Documentation/git-unpack-objects.txt
+++ b/Documentation/git-unpack-objects.txt
@@ -8,7 +8,7 @@ git-unpack-objects - Unpack objects from
SYNOPSIS
--------
-'git-unpack-objects' [-q] <pack-file
+'git-unpack-objects' [-n] [-q] <pack-file
DESCRIPTION
@@ -19,6 +19,10 @@ one-object" format in $GIT_OBJECT_DIRECT
OPTIONS
-------
+-n::
+ Only list the objects that would be unpacked, don't actually unpack
+ them.
+
-q::
The command usually shows percentage progress. This
flag suppresses it.
diff --git a/unpack-objects.c b/unpack-objects.c
index 8ae1a1c..8490895 100644
--- a/unpack-objects.c
+++ b/unpack-objects.c
@@ -6,7 +6,7 @@
#include <sys/time.h>
static int dry_run, quiet;
-static const char unpack_usage[] = "git-unpack-objects [-q] < pack-file";
+static const char unpack_usage[] = "git-unpack-objects [-n] [-q] < pack-file";
/* We always read in 4kB chunks. */
static unsigned char buffer[4096];
---
0.99.9g
next prev parent reply other threads:[~2005-11-14 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 23:20 [PATCH 0/3] Documentation additions and fixes Nikolai Weibull
2005-11-14 23:20 ` Nikolai Weibull [this message]
2005-11-14 23:20 ` [PATCH 2/3] Document a couple of missing command-line options Nikolai Weibull
2005-11-14 23:20 ` [PATCH 3/3] Documentation nitpicking Nikolai Weibull
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=11320104011582-git-send-email-mailing-lists.git@rawuncut.elitemail.org \
--to=mailing-lists.git@rawuncut.elitemail.org \
--cc=git@vger.kernel.org \
--cc=nikolai@bitwi.se \
/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