Mercurial > evolve

view debian/control @ 2050:604ecce27969

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
serveronly: use the same extensions metadata than evolve This will avoid them to drift out of sync with evolve.
author Pierre-Yves David <pierre-yves.david@ens-lyon.org>
date Tue, 07 Mar 2017 13:31:19 +0100
parents fb5e479080d8
children 790feb47ec64
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: 3.9.3
Build-Depends:
 mercurial (>= 3.4~),
 python,
 debhelper (>= 8),
 python-sphinx (>= 1.0.8),
 imagemagick,
 librsvg2-bin,
 wget,
Python-Version: >= 2.6
Homepage: https://www.mercurial-scm.org/doc/evolution/

Package: mercurial-evolve
Architecture: all
Depends:
 ${python:Depends},
 ${misc:Depends},
 mercurial (>= 3.3~),
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.
 .
 It also:
  - enables the "Changeset Obsolescence" feature of mercurial,
  - alters core command and extension that rewrite history to use this feature,
  - improves some aspects of the early implementation in Mercurial 2.3.
 .
 **These extensions are experimental and are not meant for production.**