Re: [PATCH] Documentation: pruning recipe for destructive filter-branch

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 14, 2009, 05:46 UTC
Message-ID: <alpine.DEB.1.00.0902140642520.10279@pacific.mpi-cbg.de>
In-Reply-To: <20090214025115.615119bf@perceptron>

Hi,

On Sat, 14 Feb 2009, Jan Krüger wrote:

Show 7 quoted lines

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

Indeed. It is funny when some people ask, but reading it several times a week in #git makes that fun go away real quick.

Show 8 quoted lines

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

I hope not.  IIRC I set the default to 2 weeks.

*goes to read the source* Ah, that default is only set in "git gc", and "git prune" still prunes everything. So you're absolutely correct.

But maybe we do not want to direct the user to use "prune" here, but rather "gc"?

Ciao, Dscho