view MANIFEST.in @ 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 dd518437d4e0
children
line wrap: on
line source

include CHANGELOG
include COPYING
include hgext3rd/topic/README
include MANIFEST.in
include README.rst
include setup.py
recursive-include hgext3rd *.py
recursive-include tests *.py *.sh *.t

include docs/makefile
include docs/*.py
include docs/README
include docs/*.rst
include docs/static/*.svg
include docs/tutorials/*.t
include docs/tutorial/standalone.html
recursive-include docs/figures *.svg *.png
recursive-include docs/tutorial *.css *.js *.md *.py *.rst *.sh *.t

exclude docs/tutorial/.netlify
exclude .gitlab-ci.yml
exclude hgext3rd/evolve/legacy.py
exclude .hg-format-source
exclude Makefile
exclude tests/test-drop.t
exclude tests/test-oldconvert.t

prune contrib
prune debian
prune .gitlab
prune hgext3rd/evolve/hack
prune tests/blacklists