From: Junio C Hamano <gitster@pobox.com>
Date: Tue, 18 Nov 2014 20:30:54 GMT
Subject: Re: [PATCH v3 00/14] ref-transactions-reflog
Message-ID: <xmqqr3x0uu81.fsf@gitster.dls.corp.google.com>
In-Reply-To: <546BA21C.9030803@alum.mit.edu>

Michael Haggerty <mhagger@alum.mit.edu> writes:

> I'm still not convinced. For me, "reflog_expire()" is an unusual outlier
> operation, much like "git gc" or "git pack-refs" or "git fsck". None of
> these are part of the beautiful Git data model; they are messy
> maintenance operations. Forcing reference transactions to be general
> enough to allow reflog expiration to be implemented *outside* the refs
> API sacrificies their simplicity for lots of infrastructure that will
> probably only be used to implement this single operation. Better to
> implement reflog expiration *inside* the refs API.

Sorry, but I lost track---which one is inside and which one is
outside?