fold: overhaul handling of revisions with --rev (BC) The fold command parsed the revision arguments in a very peculiar and idiosyncratic fashion: if revisions were passed without a --rev argument, then they would all be extended to ".", but if they were passed with --rev, then no extension would happen. Passing revisions both with and without --rev would abort. This is inconsistent with the way all other hg commands parse revision arguments. We have several examples of command where several revisions are passed, and the --rev option is optional for specifying those revisions (update, strip, export). This patch alters the way in which fold parses its revision arguments. No distinction is made between revisions passed with or without the --rev argument. Regardless if a single or multiple revision is specified, all will be folded together into the parent of the working directory. If the --exact argument is passed, then the parent of the working directory is ignored and the specified revisions must be a single contiguous line. The docstring and tests are modified accordingly.

     1

# Copied from histedit setup.py

     2

# Credit to Augie Fackler <durin42@gmail.com>

     3

     4

from distutils.core import setup

     5

     6

setup(

     7

    name='hg-evolve',

     8

    version='4.0.0',

     9

    author='Pierre-Yves David',

    10

    maintainer='Pierre-Yves David',

    11

    maintainer_email='pierre-yves.david@ens-lyon.org',

    12

    url='https://bitbucket.org/marmoute/mutable-history',

    13

    description='Flexible evolution of Mercurial history.',

    14

    long_description=open('README').read(),

    15

    keywords='hg mercurial',

    16

    license='GPLv2+',

    17

    py_modules=['hgext.evolve'],

    18

)