git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Pieter de Bie <pdebie@ai.rug.nl>
Cc: Jeff King <peff@peff.net>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: [PATCH] gc: call "prune --expire 2.weeks.ago"
Date: Wed, 12 Mar 2008 16:20:23 -0700	[thread overview]
Message-ID: <7vtzjb34y0.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <B27EC8CF-482D-499B-B4E0-019049926C93@ai.rug.nl> (Pieter de Bie's message of "Wed, 12 Mar 2008 23:50:04 +0100")

Pieter de Bie <pdebie@ai.rug.nl> writes:

> On Mar 12, 2008, at 6:01 PM, Jeff King wrote:
>
>> On Wed, Mar 12, 2008 at 05:05:51PM +0100, Johannes Schindelin wrote:
>>
>>>> I'd really like it to be at least 2 weeks
>>>
>>> Could you back that up with an explanation, as to why?
>>
>> I assume it's "because I wouldn't want to lose work I had done within
>> the last two weeks." Yes, I know that this expiration is actually
>> after
>> the reflog has already expired
>
> Ah, I hadn't realised that. Then I don't really care, one week sounds
> fine too. 2 weeks just seemed a bit short, as the default reflog is 30
> days. But if it's 2 weeks after the 30 days, that should be more than
> enough

Wasn't the default 90 days?

In any case, after 90 days, my reading of the code is that these loose
ones become unreachable, and when we look at their timestamps, we notice
that they are already more than 2 weeks old, and they will immediately be
removed.

So it won't be "2 weeks after X", either.

  reply	other threads:[~2008-03-12 23:21 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 20:58 [PATCH] gc: call "prune --expire 2.weeks.ago" Johannes Schindelin
2008-03-12  2:13 ` Junio C Hamano
2008-03-12  2:37   ` Nicolas Pitre
2008-03-12  6:49     ` Junio C Hamano
2008-03-12 10:57       ` Johannes Schindelin
2008-03-12 15:45         ` Nicolas Pitre
2008-03-12 15:53           ` Pieter de Bie
2008-03-12 16:05             ` Johannes Schindelin
2008-03-12 17:01               ` Jeff King
2008-03-12 22:50                 ` Pieter de Bie
2008-03-12 23:20                   ` Junio C Hamano [this message]
2008-03-12 23:30                     ` Johannes Schindelin
2008-03-12 23:41                       ` Junio C Hamano
2008-03-12 16:20         ` Geert Bosch
2008-03-12 15:07       ` Nicolas Pitre
2008-03-12 15:32         ` Marko Kreen
2008-03-12 17:35     ` [PATCH v2] gc: call "prune --expire 2.weeks.ago" by default Johannes Schindelin
2008-03-12 17:56       ` Brandon Casey
2008-03-12 18:35         ` Jakub Narebski
2008-03-12 19:07           ` Johannes Schindelin
2008-03-12 19:12             ` Junio C Hamano
2008-03-12 19:38               ` Johannes Schindelin
2008-03-12 19:53               ` [PATCH v3] " Johannes Schindelin
2008-03-12 19:55                 ` Johannes Schindelin
2008-03-12 19:55           ` [PATCH v2] " Brandon Casey
2008-03-12 19:59             ` Johannes Schindelin
2008-03-12 20:25               ` Brandon Casey
2008-03-12 20:35                 ` Junio C Hamano
2008-03-12 20:55                   ` [PATCH v4] " Johannes Schindelin
2008-03-12 20:56                     ` Johannes Schindelin
2008-03-12 21:20                     ` Junio C Hamano
2008-03-12 22:40                       ` Nicolas Pitre
2008-03-12 22:50                       ` Johannes Schindelin
2008-03-12 23:13                         ` Junio C Hamano
2008-03-12 23:28                           ` Johannes Schindelin
2008-03-12 23:39                             ` Junio C Hamano
2008-03-12 23:43                               ` Johannes Schindelin
2008-03-13  9:48                               ` Wincent Colaiuta
2008-03-13 10:17                                 ` Johannes Sixt
2008-03-13  9:21                     ` Wincent Colaiuta
2008-03-13 11:11                       ` 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=7vtzjb34y0.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=pdebie@ai.rug.nl \
    --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).