[PATCH 4 of 6 V3] merge: consider successor changesets for a bare update

Pierre-Yves David pierre-yves.david at ens-lyon.org
Wed Jan 15 19:14:07 CST 2014

On 01/15/2014 04:34 PM, Sean Farley wrote:
> +                # if successors is empty here, then it has been pruned and
> +                # there is nothing to consider updating to
Well, we could consider considering the first non obsolete parent. of 
the successor of the first parent with one.
This could(must!) be done in another patches.


More information about the Mercurial-devel mailing list