From: "Jan Krüger" <jk@jk.gs>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Documentation: pruning recipe for destructive filter-branch
Date: Sat, 14 Feb 2009 02:51:15 +0100 [thread overview]
Message-ID: <20090214025115.615119bf@perceptron> (raw)
In-Reply-To: <1234545279-23153-1-git-send-email-trast@student.ethz.ch>
Hi,
On Fri, 13 Feb 2009 18:14:39 +0100, Thomas Rast <trast@student.ethz.ch>
wrote:
> Add a section about how to shrink a repository's size after running
> git-filter-branch to remove large blobs from history.
Good idea.
> +* Expire all reflogs with `git reflog expire \--expire=now \--all`.
> +
> +* Repack to remove packed objects with `git repack -ad`.
> +
> +* Prune unpacked unreferenced objects with `git prune \--expire=now`.
Is the --expire=now actually needed for prune? The way I read it
git-prune(1), it defaults to pruning everything anyway.
-Jan
next prev parent reply other threads:[~2009-02-14 1:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 17:14 [PATCH] Documentation: pruning recipe for destructive filter-branch Thomas Rast
2009-02-14 1:07 ` Junio C Hamano
2009-02-14 1:51 ` Jan Krüger [this message]
2009-02-14 5:46 ` Johannes Schindelin
2009-02-14 6:49 ` Jan Krüger
2009-02-14 11:48 ` Johannes Schindelin
2009-02-14 14:22 ` [PATCH v2] " Thomas Rast
2009-02-14 19:12 ` Johannes Schindelin
2009-02-14 19:29 ` Junio C Hamano
2009-02-14 20:56 ` [PATCH v3] " Thomas Rast
2009-02-14 19:02 ` [PATCH] gc: make --prune useful again by accepting an optional parameter Johannes Schindelin
2009-02-14 21:33 ` Thomas Rast
2009-02-14 22:05 ` Johannes Schindelin
2009-02-14 22:10 ` [PATCH v2] " Johannes Schindelin
2009-02-14 22:38 ` Thomas Rast
2009-02-15 19:33 ` Junio C Hamano
2009-02-14 21:33 ` [PATCH] " Jan Krüger
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=20090214025115.615119bf@perceptron \
--to=jk@jk.gs \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=trast@student.ethz.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.