view MANIFEST.in @ 5962:b68789e8c535

tests: spell out hg commands for readability

These are the abbreviations that are used just in a couple of places in the
tests. `hg d` is in my opinion an abbreviation of core command that everyone
should know, but I'd rather not use "unofficial" abbreviations in tests because
it takes a second to mentally expand what the command is when you're reading
it. In CLI when you type commands, it makes sense to abbreviate things to type
less. But tests are read much more often than they are written, so I'd like to
apply the same guidelines to them as to regular code: readability first.

Apart from readability, it's also consistency, because these particular
abbreviations are rare, and everywhere else the commands are spelled out.

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