[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-devel] Re: nvm.experiment.encapsulation review
From: |
Zack Weinberg |
Subject: |
[Monotone-devel] Re: nvm.experiment.encapsulation review |
Date: |
Sun, 13 Jan 2008 18:10:25 -0500 |
On Jan 13, 2008 3:13 PM, Timothy Brownawell <address@hidden> 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] Re: nvm.experiment.encapsulation review, Timothy Brownawell, 2008/01/13
- [Monotone-devel] Re: nvm.experiment.encapsulation review,
Zack Weinberg <=