On Jan 13, 2008 3:13 PM, Timothy Brownawell <[EMAIL PROTECTED]> wrote: > The reason for get_project is that it should be possible to work with > multiple policy roots, for things like merge_into_dir and whatever we > replace it with or whatever other reason someone might have for merging > across projects. (I'm thinking this could be specified as part of the > branch name, something like --branch=project#branch .) > > It looks like there aren't any major changes, just not going thru > app_state to get to things?
Right. But if there might at some point in the future be more than one live project_t per database, probably we should do the legwork to pass it down from the CMDs rather than having a db.get_project()... zw _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
