obsexc: push nothing if push fail This is closer to the future behavior with bundle2.

discovery: hook on the official discovery for obsmarker This will let the discovery be done once and used by core.

discovery: use a different setup step for discovery This will ease the dropping of the other part later.

evolve: remove unused drop random

obshash: resist to unknown revision during discovery

code movement: gather discovery code together The discovery code is the one thing that will survive the great purge.

bundle2: drop custom compat We'll rely on the core implementation to use bundle2.

drop relevant marker compat

evolve: always use the transaction version of phase movement This drop compat with all known released version of Mercurial.

evolve: drop debugobsoleterelevant Core gained this capability usig `hg debugobsolete --rev REV`

evolve: yield to relevant markers handling in core The handling of obsolescence marker is now performed in core. If we detect a mercurial with such power we skip the wrapping from evolve. This changeset also suffer from massive diff from the change in display of obsolescence marker with parent information introduced at the same time in core.

test-wireproto: adapt to output change from core

test: update test to new date formatting in debuobsolete output The date is now a first class citizen with proper formatting.

test: update help output to future 3.2

merge with stable

pkg: make tests pass using the generated tarball Exclude tests/test-drop.t and include tests/_exc-util.sh, tests/dummyssh, and hgext/simple4server.py.

compat: always call metadata as a keyword argument Those function are gaining more arguments. using keyword argument keep use safe in all version.

test: work around a bug in debugobsolete The defautl date was wrong all along. So we use a fixed date for all tests.

merge with stable

uncommit: add a --rev argument The uncommit command now taks a --rev argument. This lets restore the file content in the current commit to another revision (instead of just is parent content). This still does not touch the working directory content.\ This allow the longly awaited: hg uncommit --hidden --rev 'precursors(.)'

readme: add missing changelog entry My dear friends changelog.

merge with stable

import: handle patch with no node information patch created by old Mercurial version or other tool have no node information. We cannot create marker in this case.

import: compare binary node with binary node when using --obsolete hex(N) != N

README: fix version number

relocate: fix typo

merge back with stable

Added tag 4.1.0 for changeset 4d5d101e878f

pkg: prepare release 4.1.0

merge default into stable Release 4.1.0 is coming

evolve: adds a --confirm option This option lets the use double check if it wants the evolve operation.

evolve: gather evolve output together We stop relying on ui.status being muted when --quiet is used. Instead we use plain write and hide this behind an explicite ui.quiet check. This will help use enforcing this output in the comming --confirm mode.

doc: forgotten amend

evolve: attempt to clarify the documentation around --all and --any This have been confusing to people. We try to be a bit more verbose in the evolve help.

evolve: re enable progress for all Progress is an important information for user facing slow push.

evolve: stop pretending we are pulling markers when we don't If discovery did not found any unknown marker, we should not display the "pulling marker" message.

evolve: do not even try to pull if all remote markers are known previously we were explicitly pulling an empty bundle.

evolve: add "obsolescence" in front of marked in the previous message

evolve: make the "X markers added" message during pull important

evolve: make the "pulling obsolescence marker" message important This is likely to take some time the user needs to know what is going on.

evolve: add "absolescence" in front of markers in the message

evolve: re-introduce the "pushing 42 markers…" message Informing the user about marker behind pushed sounds a good idea.

evolve: hide the OBSEXC message behind a config option This will lets most people ignore them while keep evolve dev having a close look at them. Some of the most useful messages will be reintroduced for all in coming changeset.

evolve: move OBSEXC progress in a dedicated function This will help use to rework them.

evolve: move OBSEXC message in a dedicated function This will help use to rework them.

merge with stable

Added tag 4.0.1 for changeset e914884fb721

evolve: prepare release 4.0.1

evolve: fix distribution for 4.0.0

evolve: update readme

evolve: update tested with statement

test: apply message changes introduced by mercurial 3.1

test: use `hg log` in the `getid` function using `hg id` to retrieve full lenght node requires to use --debug. This may include debug output (regarding branch cache invalidation for example) that breaks the test. We now use `hg log` with a custom template. This is a simple, clean and robust solution.

evolve: add a tr arguement to retractboundary Mercurial core is adding a transaction argument to its phase movement function. We do the same. If Mercurial appears to be an old version (without the extra args) we call it the old way.

relocate: add transaction around phase movement cheap way to acces access to the transaction object

uncommit tr

evolve: saner locking an transaction in `hg evolve` Each trouble solved used to handle locking and transaction on its own. We now have a top level locking and transaction. This will helps use making sure phase are moved within a transaction.

uncommit: saner locking scheme (and do it in the right order in the process)

prune: lock inside the try tss…

debugrecordpruneparents: release tr the same way than the lock Nicer code is nicer.

evolve: drop useless wlock in rewrite

divergence: actually use the hint that have been around for age Having a hint in the code is good, having it displayed is usually seens as better.

evolve: rename `tr` variable (for troubled) to `tro` tro is usually dedicated to transaction.

evolve: add a custom layer around retractboundary retract boundary is about to gain a new argument in core, we need somethign to handle this