Re: reftable [v4]: new ref storage format
- From
Dave Borowitz <dborowitz@google.com>
- Date
- Aug 1, 2017, 13:54 UTC
- Message-ID
- <CAD0k6qTFV2AAbWiKvi4=OoodoXEgxswLEbraC3xP1LzvtRRaGg@mail.gmail.com>
- In-Reply-To
- <CAJo=hJv7scc1L0_MdRkFeLAJGjYm2UkTFNOgj2e4+9Zj7KSiiQ@mail.gmail.com>
On Sun, Jul 30, 2017 at 11:51 PM, Shawn Pearce <spearce@spearce.org> wrote:
> - Ref-like files (FETCH_HEAD, MERGE_HEAD) also use type 0x3.
> - Combine reflog storage with ref storage for small transactions. > - Separate reflog storage for base refs and historical logs.
How is the stash implemented in reftable? In particular, "git stash drop" needs to be able to remove an arbitrary single entry from a reflog.
I don't think the current proposal supports writing tombstones for reflog entries, so this maybe implies that "stash drop" would have to be implemented by rewriting the whole reflog for the stash ref during compaction. Can the current compaction algorithm support this?
I suppose there are more exotic alternatives: * Go back to the normal ref(log) format for refs/stash. I figure you probably don't want to do this, given that you already moved other ref-like files into the reftable in a later revision of this proposal. * Implement the whole stash storage/command in some other way that doesn't depend on reflog.