Michael Haggerty <mhag...@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? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
