Kevin started the thread, saying that the choice to store revprops in non-cp(1)-safe storage (SQLite)
was to him a major regression.
Several suggestions flew by, including:
1. Make it possible to pack revisions without packing revprops.
2. Do away with revprops/ shards, instead have ALL properties in the SQLite db.
3. Keep revprops in the DB, when they're edited store them back to plain files which 'pack' would
then move back to the DB.
I'll add my opinion shortly.
In any case, changes to f5 must be made before that format is released, so I'm marking this as a