Re: [PATCH] prune: --expire=time

From: Junio C Hamano <junkio@cox.net>
Date: Jan 22, 2007, 02:06 UTC
Message-ID: <7vwt3fx1am.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20070122015252.GA26934@coredump.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 11 quoted lines

> I was a bit loose with my phrase 'commit operation'. What I really mean
> is:
>
> $ git add file   ;# (1)
> $ hack hack hack ;# (2)
> $ git commit     ;# (3)
>
> After step (1), you have a blob in your db. If you already had that
> blob, then you have the old blob. You don't get the updated tree and
> commit until step (3). Step (2) can be hours or days. Do you really want
> to lock the repository that long?

This case does not need any locking, as blobs reachable from index are considered as "reachable" for the purpose of pruning.