From: Junio C Hamano <gitster@pobox•com>
To: Johannes Schindelin <Johannes.Schindelin@gmx•de>
Cc: "Thomas Rast" <trast@student•ethz.ch>, "Jan Krüger" <jk@jk•gs>,
git@vger•kernel.org
Subject: Re: [PATCH v2] gc: make --prune useful again by accepting an optional parameter
Date: Sun, 15 Feb 2009 11:33:37 -0800 [thread overview]
Message-ID: <7vprhjlcku.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: alpine.DEB.1.00.0902142306400.10279@pacific.mpi-cbg.de
Johannes Schindelin <Johannes.Schindelin@gmx•de> writes:
> With this patch, "git gc --no-prune" will not prune any loose (and
> dangling) object, and "git gc --prune=5.minutes.ago" will prune
> all loose objects older than 5 minutes.
>
> This patch benefitted from suggestions by Thomas Rast and Jan Krüger.
>
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx•de>
Thanks.
Being able to say --no-$opt to an OPT_STRING to NULLify a variable that
has non-NULL default value is somewhat amusing ;-)
next prev parent reply other threads:[~2009-02-15 19:35 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
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 [this message]
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=7vprhjlcku.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=jk@jk$(echo .)gs \
--cc=trast@student$(echo .)ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox