Re: [PATCH v2] Documentation: pruning recipe for destructive filter-branch
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Feb 14, 2009, 19:12 UTC
- Message-ID
- <alpine.DEB.1.00.0902142011410.10279@pacific.mpi-cbg.de>
- In-Reply-To
- <1234621328-8998-1-git-send-email-trast@student.ethz.ch>
Hi,
On Sat, 14 Feb 2009, Thomas Rast wrote:
Show 9 quoted lines
> Johannes Schindelin wrote: > > On Sat, 14 Feb 2009, Jan Krüger wrote: > > > > > Subject: [PATCH] gc: add --prune-expire option equivalent to gc.pruneExpire > > > > I like it, and if nobody beats me to it, I will add a test for this > > option tonight. > > Cool, then let's use that in the docs.
This would be needed in addition, incase that my --prune=<date> patch is taken:
diff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt index d148e58..a8ad884 100644 --- a/Documentation/git-filter-branch.txt +++ b/Documentation/git-filter-branch.txt @@ -371,7 +371,7 @@ warned. * Expire all reflogs with `git reflog expire \--expire=now \--all`. * Garbage collect all unreferenced objects with `git gc - \--prune-expire=now` (or if your git-gc is not new enough to have + \--prune=now` (or if your git-gc is not new enough to have that option, `git repack -ad; git prune`).
-- 1.6.2.rc0.367.g7f9a5