mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Robert P. J. Day" <>
To: Git Mailing list <>
Subject: [PATCH] prune: add "--progress" to man page and usage msg
Date: Tue, 21 Nov 2017 10:51:52 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.21.1711211048400.8726@DESKTOP-1GPMCEJ> (raw)

Add mention of git prune's "--progress" option to the SYNOPSIS and
DESCRIPTION sections of the man page, and to the usage message of "git
prune" itself.

While we're here, move the explanation of "--" toward the end of the
DESCRIPTION section, where it belongs.

Signed-off-by: Robert P. J. Day <>


diff --git a/Documentation/git-prune.txt b/Documentation/git-prune.txt
index 7a493c80f..a37c0af93 100644
--- a/Documentation/git-prune.txt
+++ b/Documentation/git-prune.txt
@@ -9,7 +9,7 @@ git-prune - Prune all unreachable objects from the object database
-'git prune' [-n] [-v] [--expire <expire>] [--] [<head>...]
+'git prune' [-n] [-v] [--progress] [--expire <time>] [--] [<head>...]

@@ -42,12 +42,15 @@ OPTIONS
 	Report all removed objects.

-	Do not interpret any more arguments as options.
+	Show progress.

 --expire <time>::
 	Only expire loose objects older than <time>.

+	Do not interpret any more arguments as options.
 	In addition to objects
 	reachable from any of our references, keep objects
diff --git a/builtin/prune.c b/builtin/prune.c
index cddabf26a..d2fdae680 100644
--- a/builtin/prune.c
+++ b/builtin/prune.c
@@ -8,7 +8,7 @@
 #include "progress.h"

 static const char * const prune_usage[] = {
-	N_("git prune [-n] [-v] [--expire <time>] [--] [<head>...]"),
+	N_("git prune [-n] [-v] [--progress] [--expire <time>] [--] [<head>...]"),
 static int show_only;


Robert P. J. Day                                 Ottawa, Ontario, CANADA


             reply	other threads:[~2017-11-21 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 15:51 Robert P. J. Day [this message]
2017-11-22  3:29 ` [PATCH] prune: add "--progress" to man page and usage msg Junio C Hamano

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 \
    --in-reply-to=alpine.LFD.2.21.1711211048400.8726@DESKTOP-1GPMCEJ \ \ \

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