./devel/py-hg-evolve, Experimental Mercurial extensions from Facebook

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 11.1.6, Package name: py312-hg-evolve-11.1.6, Maintainer: pkgsrc-users

The Evolve Extension extends the "changeset evolution" features of
Mercurial core. It provides a set of commands to easily mutate history as
well as the topics extension.


Required to run:
[databases/py-sqlite3] [devel/py-mercurial] [lang/python37]

Required to build:
[pkgtools/cwrappers]

Master sites:

Filesize: 844.505 KB

Version history: (Expand)


CVS history: (Expand)


   2024-12-12 00:32:48 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
py-hg-evolve: update to 11.1.6.

11.1.6

This is a bugfix release. The notable changes are: evolve won't consider
all parts of a split content-divergent if only some of them are;
obshashrange cache will simply reset if there are too many affected
ranges instead of precision-deleting them from the database, this
improves overall performance; topic stack now provides any suitable
successor for an obsolete stack base instead of raising an error, this
prevents errors in commands like `hg topics --age` in certain cases.

11.1.5

This is a bugfix release. The most notable change is the compatibility
with the upcoming Mercurial 6.9. Also the cleanup step of `hg evolve
--abort` tries to be more careful when accessing revisions that might
not exist. Documentation and tests were updated to be closer to the
modern Python packaging standards.
   2024-11-11 08:29:31 by Thomas Klausner | Files touched by this commit (862)
Log message:
py-*: remove unused tool dependency

py-setuptools includes the py-wheel functionality nowadays
   2024-08-08 10:12:54 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
py-hg-evolve: update to 11.1.4.

This is a bugfix release. The only change is compatibility with the
soon-to-be-released Mercurial 6.8.

## Evolve: 11.1.4

   * compatibility with Mercurial 6.8

## Topic 1.1.4

   * compatibility with Mercurial 6.8
   2024-06-09 23:10:55 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
py-hg-evolve: update to 11.1.3.

11.1.3 -- 2024-04-12
--------------------

topic (1.1.3)

  * topic namespaces: add hg debug-default-topic-namespace command that can
    list changesets with problematic topic namespaces (i.e. "none" and
    "default") and rewrite them

  * topic namespaces: new experimental.tns-reject-push config to make servers
    reject pushes that contain changesets with any topic namespace in commit
    extras

  * topic namespaces: slightly change .hg/topic-namespace cleanup code to be
    executed on acquiring a wlock instead of on reading .hg/topic-namespace
   2024-03-17 16:13:00 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
py-hg-evolve: update to 11.1.2.

11.1.2 -- 2024-03-03
--------------------

  * compatibility with Mercurial 6.7

  * evolve: use functions from topic extension to set current topic and tns

topic (1.1.2)

  * compatibility with Mercurial 6.7

  * topic: handle commitstatus() with opts=None for hg <= 6.5 too
   2024-02-19 13:35:42 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
py-hg-evolve: update to 11.1.1.

This is a bugfix release. Bugs related to wire protocol and topic
namespaces were fixed: `hg incoming` works correctly again
(https://bz.mercurial-scm.org/show_bug.cgi?id=6856), pushing via
ssh shouldn't produce any errors related to tns_heads method on
the peer.  `hg pick` was made to always use current topic for the
resulting changesets, including when users don't have any set (in
which case the resulting changeset will not have any topic, regardless
of what the original changeset had). Default topic namespace value
(which at first was "default", but in 1.1.0 it was changed to
"none") won't get stored on disk and will actively be removed now
(topic extension will do it for at least a couple of releases) to
avoid any confusion when using different versions of topic extension
on the same repo. There were some improvements in handling topics
and topic namespaces that aren't ASCII-only. The evolve and topic
extensions were also marked as compatible with Mercurial 6.6,
although no code changes were required.
   2023-11-15 10:30:48 by Thomas Klausner | Files touched by this commit (1)
Log message:
py-hg-evolve: add missing tools
   2023-11-13 16:01:19 by Thomas Klausner | Files touched by this commit (3) | Package updated
Log message:
py-hg-evolve: update to 11.1.0.

11.1.0 -- 2023-10-23
--------------------

  * remove deprecated evolve.serveronly extension, evolve extension is
    recommended for all users, clients and servers

  * evolve: don't warn about topics while resolving public content-divergence

  * evolve, pullbundle: drop compatibility with Mercurial 4.8

topic (1.1.0)

  * remove deprecated serverminitopic extension, topic extension is recommended
    for all users, clients and servers

  * pick: update commit message hashes like other rewrite commands

  * topic namespaces: add `experimental.tns-allow-rewrite` config option to
    check topic namespace before rewriting changesets (known limitations: does
    not prevent rebase and histedit from editing changesets outside of
    configured topic namespaces on Mercurial 5.2 and older)
  * topic namespaces: add `experimental.tns-default-pull-namespaces` config
    option to pull only certain changesets by default
  * topic namespaces: teach `hg import` and `hg export` to handle topic
    namespaces
  * topic namespaces: invalidate topic namespace cache in
    repo.invalidatecaches()

  * topic: only set topic on workingcommitctx if it doesn't already have one,
    making `hg import` always prioritize patch metadata
  * topic: properly process revbranchcache before sending it to peers
    (issue6841)

  * drop compatibility with Mercurial 4.8