Kyle Meyer <[email protected]> wrote: > Eric Wong writes: > > > But I'm deeply worried about unleashing a new on-disk format > > that's insufficient and being stuck supporting it forever > > (as I am with v1 inboxes)... > [...] > > * lei has a bunch of rough edges and I'm not comfortable declaring > > it as supported, especially when there's a risk of data loss to > > users. > > What are your thoughts on marking all things lei with a big > experimental / subject-to-change / may-eat-your-data warning?
Yes, definitely experimental and may-eat-your-data. I hope the subject-to-change bit can be minimized, though I'll drop the '<>' in "lei q" JSON before release. I'm also considering diverging from mairix in making --augment the default behavior in "lei q". That would make things significantly safer, and --no-augment would be required to clobber existing outputs. -- unsubscribe: one-click, see List-Unsubscribe header archive: https://public-inbox.org/meta/
