git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 1/2] Documentation: remove --prune from pack-refs examples

From
Jonathon Mah <me@jonathonmah.com>
Date
Jul 18, 2013, 07:11 UTC
Message-ID
<19D1767A-4C36-4A89-A9BB-9FED33289CD9@JonathonMah.com>
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: Jonathon Mah
Message 1 of 3 in “Documentation: remove --prune from pack-refs examples”
  1. 1/2 Documentation: remove --prune from pack-refs examplesJonathon Mah, Jul 18, 2013
  2. 2/2 Documentation: fix git-prune example usageJonathon Mah, Jul 18, 2013
  3. Junio C HamanoJul 18, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.