Junio C Hamano wrote:
quoted text
>> Things I'm not sure about, any further comments/discussion?
>> - default value for gc.pruneexpire
>> - special value(s) for gc.pruneexpire/--expire which mean 'do not
>>   check for the age', currently it is 'off'
>=20
> No single timeout value can be the right timeout for everybody,
> so a big debate is not useful here.  I think 1 day as you and
> Shawn did makes sense.

Not that I want to sabotage this discussion, but you have a very valid po=
int.  A timeout can always be crossed, and then bad things[tm] happen.

My idea is to create a marker file when creating (yet) unconnected loose =
objects, i.e. on commit/push/fetch.  After the ref was updated or on abor=
t, this marker would be removed.  Prune then can simply search for the ol=
dest marker and only remove objects older than this marker.

Of course this also can mean that a marker file somehow stays and prune f=
ails to clean properly, but that's still better than accidentially cleani=
ng too much.  In the case of dangling marker files, the admin would simpl=
y remove them.  rm .git/marker/* when the repo is quiet.

cheers
  simon

--=20
Serve - BSD     +++  RENT this banner advert  +++    ASCII Ribbon   /"\
Work - Mac      +++  space for low =E2=82=AC=E2=82=AC=E2=82=AC NOW!1  +++=
      Campaign     \ /
Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \