[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-devel] Re: read/write permissions
From: |
Bruce Stephens |
Subject: |
[Monotone-devel] Re: read/write permissions |
Date: |
Sat, 27 Jan 2007 12:00:00 +0000 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.92 (gnu/linux) |
Boris <address@hidden> writes:
[...]
> Out of curiosity and to understand monotone better: Do you see then
> two heads in branch B?
Yes.
> Or do heads need to have the same ancestor cert somewhere?
No.
Not currently, anyway. Identifying (at a low-level) branches by their
names is (like identifying keys by their names) probably a mistake,
and probably it'll be resolved as part of the "policy branch" stuff.
I believe that's the plan, anyway. I don't know much more than that,
but perhaps it'll involve all revisions in a branch having a common
ancestor.
Having an odd branch cert in the wrong place doesn't necessarily cause
any immediate problems: "mtn update" will still work, for example,
because it only looks at descendents of the workspace base revision.
But it would screw propagate and merge.