Which parts of Evolve can be upstreamed?

[Pierre-Yves David]

The short answer is:

They are comment in multiple source files about their status and the 
part that can be uptreamed.


For a longer answer I need to double check my notes.
On a general basis :
- The user facing command is the most "mutable" part that we will likely 
keep experimenting for a while.
- The latest upstreaming effort was around the stack concept that proved 
itself central for providing a consistent UX around `hg evolve` in 
distributed context. I would be happy to see it get to conclusion.
- The change to heads computation and checking is a good candidate for 
upstreaming is all the logic live in core and they "wrapping" in the 
extension are neither very clean nor performant

On 2/8/21 11:59 PM, Martin von Zweigbergk wrote:
> Hi,
> 
> We have talked about upstreaming the Evolve extension for years and some 
> of it has been upstreamed, but most of it remains. I think most of us 
> agree that it would be good to have it upstreamed at some point. Are 
> there some uncontroversial parts that I can start moving upstream? The 
> obslog and prune commands seem like good candidates to me. What do you 
> think?
> 

-- 
Pierre-Yves David