obsolete: move old format stuff at the end

obsolete: introduce an extension helper and use it this extension helper allow most of setup operation to be declared in place using decorator. This allow clear separation between independant part of the code. This is the first HUGE wave of changes related to this introduction. The goal is to have a clear distinction and documention of every part of this extension.

obsolete: remove 2.2 compat hack

merge with stable

Added tag 0.7 for changeset 1b2757c1bd91

changelog: update changelog for all missing version

enable: update check to ensure people use 2.3

obsolete: remove unused BC code

hgignore: ignore the "common" tests/easy_run.sh file

test: drop old BC clause

merge

evolve: make graft wrapper handle --rev

evolve: graft --continue is optional, test

evolve: avoid duplication in graft wrapper

obsolete/evolve: fix grammar in prerequisite messages

obsolete: fix doc, rebase no longer aborts with --keep

evolve: tweak and add EOL to kill warning

nopushpublish: add license en copyright notice

obsolete: simplify obsolete feature enabling We don't need setattr here

merge

amend: wrap the whole process in a single transaction.

pushkey: properly handle abort during obsolete markers push

hook: work around insanely huge value in obsolete pushkey call The value is not that useful and make shell call explode.

merge with stable

Added tag 0.6 for changeset 4a5488c01a66

obsolete: enable obsolete feature The feature is now disabled by default in core.

obsolete: improve compat with new core dump%i scheme

add nopushpublish extension.

move the extension to contrib to prepare merge with mutable history

some doc

initial import Simple extension that prevent from pushing in a publishing remote repo.

merge with stable

obsolete: fix hidden() revset The hiddenrevs set was moved from changelog to localrepository in hg@62c56c94c77e.

obsolete: improve revset online help

make compat server both compatible with "dump" and "dump%i" version

merge

qsync: ignore unexistent nodes

backout 97b75bbfacc5. Use cached version of obsolete, unstable and extinct The core version are far too slow

backout temporary fix for clone Now fixed into core

.hgignore: ignore vi swap files

obsolete: fix typos, improve messages

test-obsolete: handle local clones copying obsolete markers

obsolete: rely on core for context and reveset which exist there (this means loosing the cache :-( )

obsolete: rely on core for rollback support

obsolete: rely on core to hide extinct changeset

obsolete: Stop turning obsolete secret changesets secret Extinct changeset are not properly excluded by core.

obsolete remove unused module

obsolete: drop outdated doc

Use the core check heads mecanism to prevent zaelous warning

obsolete: rely on core to filter extinct changeset out

[temp] fix obsolete marker cloning broken in core.

Wider triggering of the debug marker abort

obsolete: fix visibleheads/branchmap wrapping

merge with stable fix and preparation

obsolete: move hint punching to push Core does not raise the warning in check heads

obsolete: doc punch the hint about hg stabilize into the push error message. The goal is to ease the transposition of to default where half of the message may be raised by core directly.

obsolete: change warning output to match mercurial core on The new messages were introduced by hg@12fdaa30063a.

doc: fix weird quote in from-mq.rst

merge with 0.5

Added tag 0.5 for changeset 7ef8ab8c6fea

some more fix

marmoute N+2 pass

[docs] obsolete: fix some typos

merge with doc fix

grmlgm edit

evolve: switch the official name for "kill" to prune doc have been updated too

doc: cleanup in caveat and 2.1 compat

doc: big update of terms and summary of the concept This is intended to be sent to the mailing list for discussion.

evolve: add the solve alias to obsolete

obsolete: adapt to core: marker are written in transaction now

obsolete: ctx.obsolete in core is not buggy anymore

merge with conflicting detection

merge with doc fix

doc: English proofreading

Move obserror warning into the obsolete extension.

evolve: warn on conflicting changeset too

obsolete: Detect conflicting changeset!

merge with stable fix

Added tag 0.4.1 for changeset 4ecbaec1d664

Ignore buggy marker in newerversion

[convert] properly exclude null successors from convertion Old remain of the old way to kill changeset.

obsolete: remove unused add2set/markerid functions

Merge with debugconvertobsolete update

docs: improve recent updates

tests: update graphlog output after hg@2e13c1bd34dc 2e13c1bd34dc displays obsolete changesets as 'x' instead of 'o'.

Added tag 0.4.0 for changeset 9bbcd2746898

obsolete: fix bug in detection of remote obsolete support We were checking again local...

adapt for new mercurial

merge with new binary format

obsolete: harden convertion from first format

obsolete: better lookuperror handling during convert

[obsolete] convert json unicode into string before creating an obsolete marker

obsolete: we are not compatible with 2.1 any more

obsolete: convert try to guess what invalid node id are invalid input are probably short version of node

obsolete: Only warn on bad obsolete marker Older version probably created invalide one.

obsolete: fix obsolete marker creation error message

obsolete: move to official binary format

merge with stable fix

obsolete: public changeset are no longer latecomer. They are plain duplicate.

merge back with stable

more README changes (oops)

Added tag 0.3.0 for changeset c046b083a5e0

README: minor changelog update

Merge default new feature in stable 0.3.0 planned

stabilize: clear error message than conflict during rebase offer no hope The warning is big and ugly. It will be removed when stab handle that properly.

doc: readme and uncommit reference

readme: explain "instalation process" if it may be called like that.

merge with stable doc update

setup: update alias with new wording

obsolete: add an hidden revset

obsolete: basic commit --amend support commit --amend still strip. but lay obsolete marker down anyway

evolve: add a prune alias for kill pro: - it's short - It's already used in version control context - it's in the same lexical field than `graft`

evolve: warn when uncommit leave an empty changeset This is intended to replace the proposed --delete flag.

evolve: improve kill testing show than uncommited changes are properly merged

oops (forget to amend)

uncommit: warn about new instability

uncommit: add --all option Convenient when combined with --exclude.

uncommit: handle bookmarks Extract the bookmarks handling code from amend and share it with uncommit.

evolve: add uncommit command

obsolete: enable rebase --keep again We still never strip anything. But using --keep on the command line dos not lay marker.