[PATCH 1 of 3 V2] amend: allow amend of non-head when obsolete is enabled

Pierre-Yves David pierre-yves.david at ens-lyon.org
Mon Dec 31 17:42:07 CST 2012


On 1 janv. 2013, at 00:29, Augie Fackler wrote:

> 
> On Dec 28, 2012, at 11:27 PM, Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:
> 
>> If obsolescence is not enabled we keep aborting. This new default behavior only
>> apply when obsolete is enabled and is subject to future discussion and changes.
> 
> I'm not quite sure what this sentence means? Is the intent of this statement that the new behavior (with obsolete enabled) is subject to change?

The new behavior (with obsolete enabled) is open to change until we offer a simple way to enable it.

> Or is the intent that the current (backwards-compatible) behavior without obsolete on is subject to change?

The current behavior is firstly a limitation of the current implementation.

All this behavior will be discussed at the sprint.

-- 
Pierre-Yves



More information about the Mercurial-devel mailing list