On Fri, Jun 3, 2016 at 11:03 PM, Michael Haggerty <mhagger@xxxxxxxxxxxx> wrote: > Since the that ref-iterator [1] changes seem to have gotten a positive > reception, let's try to keep up the momentum. I hope I'm not > overloading the review pipeline... > > I think all of the groundwork is in place now to virtualize the refs > API. This will open the way to storing refs in ways other than the > familiar loose refs / packed refs format, such as David Turner's > proposed LMDB-based storage [2]. > > This is a long patch series, but most of the patches are pretty simple > and formulaic. The goal is to implement a `ref_store`. In the language > of object-oriented programming, `ref_store` is an abstract base class > representing a reference storage backend. It provides methods to read, > write, and delete references and symrefs, and to iterate over > references, reflogs, and reflog entries, plus a number of other > things—19 methods in all. I probably don't know what I'm talking about because I don't follow your work closely enough. Please ignore if this is nonsense. But if we extend/change API, we might need to update git-for-each-ref too, to expose it to shell scripts and external commands. I guess for iteration there's nothing else more needed, but we may need to introduction new options for the storage thing, e.g. to select storage... -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html