[Monotone-devel] Re: nvm.experiment.encapsulation review

[Markus Schiltknecht]

Hi,

Zack Weinberg wrote:
> Probably it is best to get to a stopping place on the app_state
> passdown removals first, and then revisit each hack individually.

Agreed.

> I do still want to do the ro/rw_database stuff - contra the other
> thread on that, I think *even if* the database itself doesn't
> necessarily care, it would be useful for enforcing high-level
> constraints, so that we can say for instance "this subset of the
> commands is intended to work on a database which the user does not
> have write privileges for."  But I think it should wait till after
> this branch is merged.

Okay.

> They're not dead, but they might be sleeping until the stars are
> right.  IIRC we got stuck on very basic design arguments at the last
> summit and there's been no forward progress since.

Next summit is coming up ;-)

> db-compaction is another one of my pet wishes, I'll see if I can find
> time to look at it.

I'll try to merge it and comment more on what I've done, so as to give 
you a better start than with nvm.ee.

> I wonder is CVS import actually all that important anymore?  Should we
> rather be concentrating on SVN, git, and mercurial compatibility?

Well, at least to me and to Kelly, is still *is* pretty important.

Regards

Markus