monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Timothy Brownawell
Subject: Re: [Monotone-devel] Re: [RFC] versioned policy -- introduction
Date: Fri, 08 Sep 2006 00:36:56 -0500

On Thu, 2006-09-07 at 22:18 -0700, Nathaniel Smith wrote:
> > Also, is this one trust seed per database?  So does this force one
> > database per project (quite probably a good way to do things, but not
> > the way everyone works currently)?
> 
> Maybe!  Or maybe not; nothing is set in stone yet.  But a 1-1
> database<->trust seed relationship is tempting.  For pretty much any
> operation, we need to know what trust seed to use, up-front -- this is
> dramatically simplified if there is only ever one trust seed to choose
> from.  And one database per project already seems to be the best
> practice anyway; I don't generally feel guilty about encouraging
> people to use best practices.

I'd think that that would make things like using merge_into_dir across
projects (like if upstream for botan or lua or sqlite was in mtn) a bit
of a pain.

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





reply via email to

[Prev in Thread] Current Thread [Next in Thread]