From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Johannes Sixt <johannes.sixt@telecom.at>,
git@vger.kernel.org, pasky@suse.cz
Subject: Re: [PATCH] Add "--expire <time>" option to 'git prune'
Date: Thu, 29 Nov 2007 16:13:47 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711291613260.27959@racer.site> (raw)
In-Reply-To: <20071129151211.GB32296@coredump.intra.peff.net>
Hi,
On Thu, 29 Nov 2007, Jeff King wrote:
> On Thu, Nov 29, 2007 at 02:21:23PM +0000, Johannes Schindelin wrote:
>
> > This patch adds a mode to expire only loose, unreachable objects
> > which are older than a certain time. For example, by
> >
> > git prune --expire 14.days
> >
> > you can prune only those objects which are loose, unreachable
> > and older than 14 days (and thus probably outdated).
>
> Does this now make git-prune safe for automatic running?
>
> I suppose you could still be actively manipulating refs that point to
> very old objects.
That's why I want to have it configurable from git-gc.
Ciao,
Dscho
next prev parent reply other threads:[~2007-11-29 16:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 11:25 [RFC] Alternates and broken repos: A pack and prune scheme to avoid them Johannes Sixt
2007-11-18 18:39 ` Junio C Hamano
2007-11-18 20:01 ` Johannes Sixt
2007-11-18 20:10 ` Junio C Hamano
2007-11-29 3:41 ` [PATCH/RFC] Teach repack to optionally retain otherwise lost objects Johannes Schindelin
2007-11-29 6:15 ` Junio C Hamano
2007-11-29 11:57 ` Johannes Schindelin
2007-11-29 14:21 ` [PATCH] Add "--expire <time>" option to 'git prune' Johannes Schindelin
2007-11-29 14:35 ` Johannes Sixt
2007-11-29 15:22 ` [PATCH v2] " Johannes Schindelin
2007-11-29 15:12 ` [PATCH] " Jeff King
2007-11-29 16:13 ` Johannes Schindelin [this message]
2007-11-29 20:06 ` Junio C Hamano
2007-11-29 20:59 ` Johannes Schindelin
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=Pine.LNX.4.64.0711291613260.27959@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.sixt@telecom.at \
--cc=pasky@suse.cz \
--cc=peff@peff.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).