From: Jonathon Mah <me@JonathonMah.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: [PATCH 1/2] Documentation: remove --prune from pack-refs examples
Date: Thu, 18 Jul 2013 00:11:58 -0700 [thread overview]
Message-ID: <19D1767A-4C36-4A89-A9BB-9FED33289CD9@JonathonMah.com> (raw)
The option has been the default for a while, and doesn't otherwise
appear in the page.
---
Documentation/git-pack-refs.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-pack-refs.txt b/Documentation/git-pack-refs.txt
index f131677..154081f 100644
--- a/Documentation/git-pack-refs.txt
+++ b/Documentation/git-pack-refs.txt
@@ -33,8 +33,8 @@ Subsequent updates to branches always create new files under
`$GIT_DIR/refs` directory hierarchy.
A recommended practice to deal with a repository with too many
-refs is to pack its refs with `--all --prune` once, and
-occasionally run `git pack-refs --prune`. Tags are by
+refs is to pack its refs with `--all` once, and
+occasionally run `git pack-refs`. Tags are by
definition stationary and are not expected to change. Branch
heads will be packed with the initial `pack-refs --all`, but
only the currently active branch heads will become unpacked,
--
1.8.3.3.754.g9c3c367
Jonathon Mah
me@JonathonMah.com
next reply other threads:[~2013-07-18 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 7:11 Jonathon Mah [this message]
2013-07-18 7:12 ` [PATCH 2/2] Documentation: fix git-prune example usage Jonathon Mah
2013-07-18 17:55 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19D1767A-4C36-4A89-A9BB-9FED33289CD9@JonathonMah.com \
--to=me@jonathonmah.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).