[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] multiple (3+) ancestors
From: |
Timothy Brownawell |
Subject: |
Re: [Monotone-devel] multiple (3+) ancestors |
Date: |
Fri, 09 Feb 2007 13:28:14 -0600 |
On Fri, 2007-02-09 at 11:20 -0800, Zack Weinberg wrote:
> On 2/9/07, Timothy Brownawell <address@hidden> wrote:
> > On Fri, 2007-02-09 at 10:53 -0800, Zack Weinberg wrote:
> > > On 2/8/07, Markus Schiltknecht <address@hidden> wrote:
> > > > http://www.venge.net/monotone/wiki/MultiParentWorkspaceFallout on the
> > > > wiki currently states: "A revision can't have more than two parents."
> > > > While Graydon recently answered me, that monotone itself does not pose
> > > > such a limit.
> > >
> > > Graydon is mistaken. revision_t::check_sane() [...]
> >
> > That's not a limitation of monotone, just our current code. There's no
> > real reason not to remove that limitation...
>
> ... I don't see a good reason *to* remove that limitation, though. I
> call YAGNI.
I think its certainly possible that it'd be useful for whatever trust
scheme we come up with to be able to directly record any n-parent merges
that were needed instead of having to split them up. Of course, whether
it's convenient enough to go to all that trouble would be a different
question, that even more has to wait until we actually know what we're
doing...
--
Timothy
Free (experimental) public monotone hosting: http://mtn-host.prjek.net