view debian/control @ 6935:954d7ea5cd67 stable tip

stack: when stack base is obsolete, pick any successor, even if at random There are situations when s0 is obsolete and we also cannot pick just one successor for it to use in stack. In such a case, let's pick the "latest" successor from the first set. We're assuming that obsutil.successorssets() returns data in the same order (it should, since it makes sure to sort data internally). Keeping that in mind, while the successor picked for s0 by this code is not based on any sort of sophisticated logic, it should nonetheless be the same every time. This patch is probably not going to completely break anything that was previously working fine, because the previous behavior was to just abort with an exception.
author Anton Shestakov <av6@dwimlabs.net>
date Sat, 16 Nov 2024 17:01:02 +0400
parents 4f051e30fcae
children 33d5071edd05
line wrap: on
line source

Source: mercurial-evolve
Section: vcs
Priority: optional
Maintainer: Logilab <contact@logilab.fr>
Uploaders:
 Julien Cristau <julien.cristau@logilab.fr>,
 Pierre-Yves David <pierre-yves.david@logilab.fr>,
Standards-Version: 4.3.0
Build-Depends:
 mercurial (>= 4.9),
 python3,
 debhelper (>= 10),
 dh-python,
 python3-sphinx <!nodoc>,
 imagemagick <!nodoc>,
 librsvg2-bin <!nodoc>,
 graphviz <!nodoc>,
X-Python3-Version: >= 3.6
Homepage: https://www.mercurial-scm.org/doc/evolution/
Vcs-Browser: https://www.mercurial-scm.org/repo/evolve/
Vcs-Hg: https://www.mercurial-scm.org/repo/evolve/

Package: mercurial-evolve
Architecture: all
Depends:
 ${python3:Depends},
 ${misc:Depends},
 ${sphinxdoc:Depends},
 mercurial (>= 4.9),
Built-Using: ${sphinxdoc:Built-Using}
Description: evolve extension for Mercurial
 This package provides the experimental "evolve" extension for the Mercurial
 DVCS.
 .
 This extension provides several commands to mutate history and deal with issues
 it may raise.