Re: [Monotone-devel] Re: [RFC] versioned policy -- introduction

[Timothy Brownawell]

On Fri, 2006-09-08 at 16:12 +0100, Bruce Stephens wrote:
> Timothy  Brownawell <address@hidden> writes:
> 
> > On Fri, 2006-09-08 at 01:05 -0700, Zack Weinberg wrote:
> 
> [...]
> 
> >> Seems like what is really wanted there is a cross-database merge,
> >> where you declare some mapping  between trust in the upstream database
> >> and trust in yours (I think the security literature calls this
> >> "federation") and use that to copy across the bits you want.  I'd
> >> think this would be easier in monotone than in many other systems due
> >> to the content addressing...
> >
> > er, so monotone would have to learn to work with multiple databases,
> > now?
> 
> I hope not.  I was imagining some special command that would pull in a
> branch marking it in some way as imported for the purpose of
> merge_into_dir.

Well, ideally we'll get rid of die-die-die lifecycle merging, and after
that happens it would be reasonable to extend things so that you can
propagate in either direction across a merge_into_dir and it will do the
right thing (ooh, asymmetrical merging. scary.). At which point
requiring special import/export commands for merging across projects
becomes even more of a pain.

Tim
-- 
Free (experimental) public monotone hosting: http://mtn-host.prjek.net