Re: [PATCH] technical doc: add a design doc for the evolve command

From: Stefan Xenos <sxenos@google.com>
Date: Nov 20, 2018, 17:27 UTC
Message-ID: <CAPL8ZiuVbrXLKaJe2iBe-nDqCe9h+GiVDUDQmdnfDrCJUPHJvA@mail.gmail.com>
In-Reply-To: <xmqqmuq4d0h5.fsf@gitster-ct.c.googlers.com>

> I was trying to see if this is something we can leave out to limit the initial scope.

Oh, in that case, "yes". :-) If there's a need to cut something, origin parents would be a viable candidate.

I was thinking that this file could document the final goal so that if anyone else wanted to contribute to the implementation, we would be heading in the same direction. It seems reasonable that an early implementation may omit origin parents. Since the actual implementation will lag behind the spec, I'll add a status section to the top of the document where we can describe the delta between plan and implementation.

Also, I'm now convinced we're talking about the same thing. :-)

Show 5 quoted lines

> > Are you claiming that this is undesirable, or are you claiming that
> > this could be accomplished without origin parents?
>
> I was trying to see if this is something we can leave out to limit
> the initial scope.