[PATCH 1 of 2 standalone-strip] mq: extract strip as a standalone extension (issue3824)

Kevin Bullock kbullock+mercurial at ringworld.org
Wed Sep 25 17:04:31 CDT 2013


On 25 Sep 2013, at 4:53 PM, pierre-yves.david at ens-lyon.org wrote:

> # HG changeset patch
> # User Pierre-Yves David <pierre-yves.david at ens-lyon.org>
> # Date 1380144102 -7200
> #      Wed Sep 25 23:21:42 2013 +0200
> # Node ID f2d6590c1873f5d9fbd903a2ea467a19de4d4c13
> # Parent  72982741c525e1d0b06096bc7eafc780a4f2274f
> mq: extract strip as a standalone extension (issue3824)
> 
> Strip now lives in its own extension. The extension is surprisingly called `strip`.
> The `mq` extension force the use of the strip extension when its enabled. This
> is both necessary for backward compatibility (people expect `mq` to comes with strip) and
> become some utility function used by `mq` are now in the strip extension.

Per Augie's suggestion, can we see this as several patches, each moving a single function over into the new extension?

Patch 1 can add an empty strip.py extension and the necessary changes to mq.py to load it. Then move one function at a time, with the last one being the command itself, adding the documentation to mq.py at the same time.

pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
Kevin R. Bullock



More information about the Mercurial-devel mailing list