test conflicting conflicting (sic) resolution

Added tag 1.0.0 for changeset b18b00036355

pkg/debian: Debian packaging This change add the necessary files to create a debian package for the evolve extension. I do not care about the rest.

tests: remove unused required tools The original mercurial test use much more stuff than us.

pkg: exclude tests for unpackaged extension the old obsolete format BC and qsync are not included in this package. exclude related tests.

test: remove unused obsolete extension in the tutorial

docs: add missing blank line after Copyright notice

hgignore: ignore compiled tutorials

doc: remove spurious print in test2rest.py

pkg: add proper MANIFEST.in

doc: long desc update

remove old qsync enable file

setup: fix version number to 1.0.0 0.1.0 was release times ago

Conditionnaly add the `hidden` revset symbol Mercurial Core#default now have it (but 2.3 don't)

ensure all file have a copyright notice

add COPYING File with the license

evolve: usual syntax/grammar errors/long lines cleanup

evolve: simplify locking in _solveconflicting()

fold: simplify locking

touch: simplify locking pattern

evolve: factor out copy/paste in obssummary()

evolve: avoid 'any' argument name in _picknexttroubled()

evolve: localrepo.revs() already returns a list

evolve: compute "troubled" revs in stabilize only when necessary

evolve: move _stabilizableunstable() with related functions

test-tutorial: stop using enable.sh, removed by 53d7e3413337

evolve: add touch and fold to command that may create troubles They should raise warning about it too.

doc: add missing image

doc: fix emphasis

doc: remove toc reference to dead file

setup.py: remove setuptools related info bad setuptool bad.

doc: add more warning This is not "stable"

update implementation details

Doc: several update

Prepare 0.1.0 by merging default into stable stable is now compatible with 2.3 only.

pkg: rewrote the install process We now have a single extension. - enable is dropped - a setup.py is added - the doc is updated to reflect this

evolve: add the odiff alias

[pkg] Add a setup.py

Ignore build directory

update documentation

doc: some terms update

rename `stabilize` to `evolve` stabilize keep being valide but as Matt still like "Changeset Evolution" as a name evolve make more sense. Stabilize is a bit too tight to unstable too.

merge evolve and obsolete

sort import

Fix mercurial version check

Start a mercurial 2.2 branch This branch contains and old version compatible with mercurial 2.2. It's less complete and safe than later version.

update changelog

fix typo

evolve: stabilize now handle conflicting changeset Some a lot of rough edge but it just damn work.

stabilize: conflicting changeset are considered if "." if not unstable changeset are found, the current parent directory may be stabilize if conflicting

Introduction of olog as an alias This will won't stay as such long.

evolve: fold command First crude version of a fold command

evolve: touch command command to easily revive a changeset.

obsolete: ignore hidden changeset when resolving `branchname` revision

obsolete: add obsolete data to summary.

update changelog for upcoming 1.0

merge with stable improvement

[evolve] amend: display proper error message while trying to amend non ancestor

[evolve] amend: check phase before starting the transition We better abort before starting a useless transaction.

test: turn the base public usefull for followup that test phases enforcement.

obsolete: prevent bare hg update to select hidden changeset The issue remain with branch name.

obsolete: prevent rebasing of public changeset Because we force keep we have to check this on our own.

obsolete: warn when the whole rebase set was remove because extinct

obsolete: use flag to detect that a obsolescence marker fix a latecomer Otherwise latecomer fix will be latecomer too.

stabilize: handle latecomer Merge are not handled yet.

stabilize: rework stabilize code to allow selection of latecomer and conflicting They are still unhandled but the tool now explicitly state this fact.

obsolete: add a "troubled" revset returns all changeset with troubles whatever the trouble is.

stabilize: handle killed changeset in stabilize.

stabilize: --continue support !!! Based on graft one.

stabilize: rename "node" variable to "orig" It's a not a node at all. this is a context.

obsolete Move merge failure handling into stabilize code This violate less Layer. For this purpose we crate an easy to recognize Exception Class.

obsolet: fix extension help code about extension wrapping

merge

obsolete: filter out nullid from possible successors This have several bad effect as wrong late comer detection.

obsolete: more typos and cleanup

obsolete: fix indentation in obsolete import block

obsolete: fix docstrings

obsolete: simplify module docstring

obsolete: simplify rebase wrapping code and change relation creation We have don't have changeset simply pruned by rebase. When they disapeared, that means that destination is a valid successors for them.

obsolete: more comment

remove useless function It has no user left and no purpose in live.

add cleanup todo

more doc and cleanup

obsolete: document the cache stuff

obsolete: Improves cache invalidation logic Filecache are not the same that cache property. This can probably be improved

obsolete: some more movement

obsolete: move caches on obsstore No need to clutter local repo

obsolete: remove legacy revset

obsolete: enforce pdiff and pstatus alias in the extension

drop repo.addobsolete We now use createmarkers directly. No black magic with nullid is done anymore.

obsolete: remove usage of addcollapsedobsolete

obsolete: extract high level marker creation in a dedicated util function This prepare the dooms of repo based method.

obsolete: remove debugsuccessors This was kinda duplicate of core "debugobsolete"

obsolete: tag more function for disapearance

obsolete: reorder import

obsolete: some more dead code

obsolete: sort all code Move (splitting some function) all code in dedicated section The hook wrapping have disapeared in the process.

obsolete: remove unused repo method

obsolete: clean up import

obsolete: more BC drop

obsolete: move version checks at the start of the file

obsolete: some more comment

obsolete: add and use templatekw decorator

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.

[obsolete] fix revset error message

evolve: warn when latecomer changeset are created

obsolete: detect late comer during push

obsolete: add latecomer computation and display

obsolete: add precursors and successors revset.

update revset vocabulary to use precursors, successors

obsolete: remove unused variable in rebase wrapping

evolve: tidy up a bit - long lines - extra blank lines - commands options descriptions

obsolete: make collapse create less markers Collapsing A and B into C was registering: A -> C B -> C A -> B At this point, the last relation brings nothing and is removed for the sake of simplicity: A -> C B -> C test-evolve.t is slightly modified as one of the relations let stabilize compute a target outside of the parent revision tree. This is a stabilize bug, not trivial to fix, so let's tweak the test for now.

obsolete: remove unused code from reposetup()

obsolete: suspended changeset with secret only children should be secret too test-obsolete-push.t: exhibit outgoing bug with suspended changeset in this case

obsolete: add 'obsolete' keyword The obsolete keyword displays the node status among 'stable', 'unstable', 'suspended', 'extinct'.

obsolete: unify collapsed revisions markers handling When collapsing A, B and C into D, amend was registering: A -> D B -> D A -> B C -> D A -> C while the rebase wrapper was doing: A -> D B -> D C -> D At this point, I have no argument to favor one or another or even a new one like: A -> B B -> C C -> D so I am aligning the rebase implementation on the older amend one. At least we can now change them all at once.

rebase: improve invalid revisions filtering - Filter rebasestate nullmerge and unrebased revision before considering updating obsolete. This simplifies the handling of obsolete and make it ignore unrebased revision rather than extinguishing them. - Apply obsolete markers only if rebasestate is not empty, testing rebasetarget was irrelevant.

test-evolve: extend output and exhibit an amend bug The extended section shows the parent revision stabilizing itself on another revision, without --any. In theory, only descendants of the parent predecessors or of its descendants should be stabilized, and be stabilized in parent subtree. Unfortunately, stabilize implementation correctly picks the changesets to stabilize but not their target. This problem is aggravated by amend registering too many obsolete markers which prevents the stabilize selection heuristic to prune several changesets.

evolve: remove --change . == --change .^ crazyness

evolve: use explicit phase constants

[doc] update readme

[doc] have people update on stable after cloning

merge with fix

merge with fix

[qsync] fix: 'newerversion' expect node id, not hexid

merge back with stable tag

Added tag 0.2.0 for changeset d3f20770b86a

Merge with Patrick improvement

obsolete: do not obsolete rebase --detach nullmerge revs Rebase state contains the changesets to rebase as well as 'nullmerge' entries used drive the merge strategy. These nullmerge were not rebased and should be ignored, and certainly not be marked obsolete.

evolve: fix relocate() with removed revision relocate() was not handling the case where the rebased revision was discarded and was raising when trying to update the phase of None.

test-obsolete-rebase.t: test --abort and --continue

obsolete: handle rebase --collapse Recording obsolete in concludenode() did not work for --collapse because only the first revision was passed to the call. The new strategy is to track the rebase state in defineparents() and concludenode() and to create markers only after a successful non-abort call. In theory, this should also fix --continue/--abort cases. The change in test-stabilize-order.t comes from concludenode() no longer creating obsolete marker. stabilize command was actually duplicating markers, once in concludenode(), once explicitely.

test-stabilize-order.t: trace obsolete markers Will prevent breakage in rebase.concludenode() overriding.

test-obsolete-rebase.t: move --keep test from test-obsolete.t

obsolete: handle rebase removing empty changesets The new revision identifier returned by concludenode() was None and was not correctly translated to nullid.

obsolete: add or fix debug commands help

obsolete: do not duplicate command help

obsolete: use new-style command registration

obsolete: make rebase abort with --keep obsolete modifies rebase to mark rebased changesets obsolete instead of stripping them, which makes --keep irrelevant.

obsolete: fix rebase wrapping ui and repo arguments were swapped which made --keep calls traceback.

obsolete: add debugsuccessors command It dumps obsolete changesets and their successors.

evolve: add alias for kill and stabilize

merge with 0.1.0 tag

Added tag 0.1.0 for changeset 6c6bb7a23bb5

stabilize: improve unstable selection heuristic Without argument, stabilize was picking the first in: "unstable() and ((suspended() or obsancestors(::.))::)" which usually returned the "oldest" unstable revision in parent predecessors descendants. This revision is interesting because it usually gives "soft" merges but rebasing it left the working directory on a remote branch, which was very confusing. The new heuristic picks an unstable changeset which can be rebased on top of the parent revision, or on top of one of its descendants (selected in revision order). This has the advantage of selecting a revision which can be rebased on the current subtree, and leave the working directory in a more convenient location.

amend: remove useless repo.changelog alias

README: some more changes

merge with Arne changes

amend: do not traceback on no-ops If rewrite() generated changeset happened to be an existing one, the call would traceback when trying to obsolete the changeset with itself. Instead, leave gracefully, marking any intermediate changeset extinct.

amend: do not rely on revsingle() default for --change

amend: drop --branches, pick it from working directory The amended changeset branch was picked either from --branch or from the first parent, but the actual working directory branch was ignored. The behaviour is changed so the amended revision branch is picked from the intermediate revision, which branch comes from the usual working directory rules. --branch is thus replaced by "hg branch".

.hgignore: add .rej/.err/.orig and emacs tmp files

added “pull here is OK, too” to the README.

evolve: fix stabilize --any short option It was displayed as --A instead of -A.

tutorial: zsh fix

Fix amend and relocate who picked phases data after extinct wher made secret

zsh does not like "`" in << EOF

readlinks does not do what we wnat on BSD

evolve: update rebase usage to match 2.3

obsolete: fix error in cache invalidation

[obsolete] fix new api: be more flexible on rebase's buildstate signature Introduced by `d1afbf03e69a@mercurial <http://selenic.com/repo/hg/rev/d1afbf03e69a>`_

[obsolete] fix new api: use the new phase cache api Introduced by `b6081c2c4647@mercurial <http://selenic.com/repo/hg/rev/b6081c2c4647>`_

[qsync] abort properly of a patches repository does not exists

[doc] Specify that tuto hg configuration is used for testing.

qsync: fix mq commit message generation A CR was missing when both applied and ready to review patches are generated during a single qsync.

[doc] changes location of repo We now have a "stable" repo on bitbucket and a dev repo on logilab hg lab.

change version definition

doc: idea about OnDisk Storage

doc: add the RoadMap

[doc] add Question and Answer about Obsolet Marker Implementation

fix typo in file name

[doc] change doc generation directory

[doc] add good practice section

[doc] fix unstable code block

[readme] fix stupid typo

more read me update

update README

[doc] fix tutorial warning

[doc] add `.t` to `.rst` converteur Update make file accordingly.

[doc] fix bad include

[doc] add a simple make file

docs: proof-read and review

restore unstability content

less verbose table

[doc] update tutorial text.

proof-read documentation and docstrings

doc: several update and review.

obsolete: export pretty printed json Will help unavoidable hand fixing.

accept test change (not very happy about it)

new obsolete store The new formats allows multiple "new" changeset and various meta-data. Forcing extinct to secret phase happen now on an irregular basis A command exist to migrate to the new format

enable.sh: enable rebase because evolve need it

ignore .pyc files

doc: unstability principle

qsync: support for synchronisation with applied patches from outer space and more :more: - also add some tests - kill OLDBRANCHNAME - several minor cleaning

evolve-amend: properly handle amending file renames and additions.

obsolete: do no complain when push create a new head but obsolete an old one. Do not read the code or your eyes will burn. The (+1 heads) message still appear (see mercurial issue 3394).

obsolete: refuse to push unstable changeset without -f We do not alter phase of suspended and unstable changeset anymore. But push refuse to push them without force. The extinct part of the history stay secret for simplicity shake.

qsync: add a warning file in qsync changeset.

obsolete: fix changelog reload This changelog was not properly reloaded. This leaded to bug with rollback and strip.

obsolete: do not warn about unpushed extinct changeset.

obsolete: add an extinct property on context

obsolete: to not overwrite cancopy This does not bring anything and this confuse verify.

evolve: issue the "%i new unstable changeset" in more place most command able to create unstability now issue the warning

obsolete: blindly obsolete unstability cache when changeset are added

tutorial: make it pass again More work is needed but the tutorial work as a functionnal test.

docs: fix broken alias for qseries template for description in `{desc}` not `{description}`

fix enable.sh script it was printing the mercurial version in to HGRC file

test: graphlog honor --hidden honor in 2.2

obsolete: fix rollback wrapper for 2.2-rc

2.2 compat: nodemap.get take a single argument now.

[obsolete] add supprt for futur Hg 2.2

[obsolete] simplify by using the Hg 2.1 api

qsync: display short node repr on error

FAQ: add en entry about rebasing after a pull

FAQ: typos

FAQ: small typo

stronger try except for store cache

amend: add a warning after amend added unstablility

ignore merge in qsync

add a known issu

merge arne change

docs: Merged obs-concept changes by hand.

Backed out backout changeset f047cd4f1235

fix qsync-enable.sh extension name is qsync not obsolete (terrible terrible trouble)

follow-up on evolve-collaboration

add split example

doc: some minor fixes

merge with arne change

merge with backout

backout obs-concept.rst changes too much conflict with changes in another branch

docs: polish for glossary

docs: polishing of from-mq.

docs: fix typos in evolve collaboration.

docs: added a question: split changesets?

docs: fix typos in the FAQ

evolve: logopts was called logopt.

docs: typo

docs: polishing of obs-concept.rst

docs: some fixes on the index and the first half of the obsolete concepts.

merge

many fixes

doc: replace ">" by ">>" (oups)

doc: add reference to qsync

merge with auc improvement

auc improvement of the doc

add more canveas

add auc user story

big doc update

title reorganisation

improved intro about evolve

more doc update

add svg for schema

More doc and index with sphynx

mercurial 2.1.2 compat

really add qsync enable

this is an FAQ not a tutorial

add version info

some more doc update

add a qsync-enable

use cat in enable.sh

add qsync extension to mutable history

very cruse evolve tutorial

evolve: improve graft handling of -O we now resolve changeset reference before graft

obsolete: improve rebase compat

import some doc

obsolete: define an unstable property on context

kill: properly get revision pointed by --new Previously the raw value on --new ended in the obsolete file.

stabilize: proper --quiet behavior

stabilize: stabilize my topological branch only if not stated otherwize.

Add a bosancestors revset

add an obsolete parent revset and related alias

overwrite user not date

remove useless hidden related stuff in amend

add user to the list of option prevent the "no change found" message to show up

evolve that does something \o/

stuff that pass

fix evolve test

add test for revset

obsolete: add revset for various error case

add a simple script to help people enabling the extension.

rename evolution to evolve too much confusion with the email client

obsolete: alter newerversion return prepare ability to split and return kill information.

keep branch on amend

evolution: add a --new argument for kill

obsolete: lazy relation adding

obsolete: remove outgoing filtering as it is taken care but forcing obsolete to be secret

Add gup and gdown command to mimic qpop and qpush command

obsolete: stop using rev as it rebuild the cache every time there is a fault We now use nodemap directly

remove dead comment

obsolete: clever obsolete not in secret detection to avoid locking the repo without a reason.

obsolete: fix locking when enforcing obsolete as secret

Locking while writing obsolete data.

obsolete: improve locking when writing obsolete data

obsolete: remove public revset (it's now expected to be in core)

evolution: proper locking scheme (maybe a bit zelous with wlock and lock)

edit option \o/

Add a -o and -O option to graft.

Add a -o option to commit

add an option to ensure unstable are secret

nicer hiddenrevs init

adapt evolution to phase in core.

adapt obsolete to phase.

more removal from phase in core.

remote the states extention. (phase are now in mercurial core)

obsolete: smarter initialisation of obsolete stuff from disk.

Properly inherit phase of relocated changeset.

Add a states.bypass option to push without touching state.

Allow setstate with the last non trcked state.

Add missing break line at the end of a debug message

propertly handle -m and -l option

amend: add a --branch option

monkeypatch strip fancier

fix strip - seems good enougth now

[states] fix strip but one thing still stay wrong (see test test-state-strip.t)

[states] fix strip but a case still does not work (see test test-state-strip.t)

[states] make enabling state saftier * Fix the lower state heads while enabling a state. * Add a --clever opiton that do not fix the lower heads (as earlier) * Add test for enable/disable state

[states] make disabling state saftier It is not allowed to disable a state that is not empty because "Explicit is better than implicit". A hint is displayed to help the user.

[states] add --exact option to `hg <state> <nodes>` that allows to backward states bondaries

improve tuto

[evolution:evolve] use short hex instead of rev number

docs: Small tutorial

[evolution:amend] prevent amending immutable changeset.

[evolution:relocate] propertly interpred src and destination.

[states] do not activate deactivated state with ``hg states --off <state>`` previously: $ hg init alpha $ cd alpha $ hg states --off draft $ hg states published draft now: $ hg init alpha $ cd alpha $ hg states --off draft $ hg states published

[obsolet] base64 encore obsolete rel for pushkey Yop this is ugly

[evolution] first workign draft of a relocate function The relocate function is a lighter rebase.

[evolution/obsolete] very experimental and crude evolve support.

[obsolete] code section comment for repo subclassing

[obsolete] vocabulary update suggestion

[obsolete] rebase always keep changeset.

Compat with mercurial 1.9.2

[evolution] imported hg amend from parren works (this rocks heavily)

Basic kill command

[obsolete] add kill support

[obsolete] issue a warning when parent of current directory is obsolete.

[states] add some documentation for extension wrapping

[states] update qimport code so it doesn't fails on qimport without -r

mention plan for hook in the documentation

[obsolete] published changeset can't be obsoleted states extension is now required. A warning message is emitted when obsoleting a published changeset.

[obsolete] update docstring

[obsolete] remove useless code.

[obsolete] rationalize doc header.

[obsolete] Move extension compat code

[obsolete] extract serialization logic.

[obsolete] update doc

[state] Update doc on the mutable property of state (and the way it's implemented)

[state] add mutable property to state object.

[states] add a todo related to MQ

[states] fix a bug with rebase --detach There is unexpected (for me) content in state.

[states] add mq support

[states] add rebase support.

[states] move IO logic outside the repository subclass This is meant to lighted this part a bit

[states] add a small paragraph about controlling permision to move the boundary

small refactoring and big doc update. Sorry for the big commit crecord one so much diff seems to confuse my powerbook to death :-/

move part of the readme about states in states itself.

[obsolete] Fix pushkey

Use dedicated mechanism to report pushkey success

[obsolete] Update pushkey code

Update pushkey code to be able to push ready heads too.

Make states more resilient to missing head In particuliar pushkey is now more robust (with a very naif approach)

reorganise code

Rollback support

move extensions in a hgext directory

clone support

Change test output again (get a better distinction between rev number and hash to detect hidden changeset)

update README

Don't overwrite non local repo.

Do not propagate obsolete changeset

include hash in test.

Add pushkey support for pull and push

more comment

Make rebase set-obsolete relation

Do not hide current and bookmarked

proper computation of hidden changeset.

revset

Fix

Documentation !

Complete a Readme sentence.

Spelling fixes

Add a few information about obsolete relation.

Add some doc.

obsolet: basic support (hide changeset)

tag: do not publish for local tag.

fix outgoing filtering.

fix nodestate computation

published is always enabled.

Working directory is draft.

add a states command The command list enabled state and allow to enable, disable state. test have been update to use it.

Add docstring to move head command.

Move state activitation in a dedicated file repo-side The main issue with having state information is hgrc is that hgrc can be ignored for trust reason.

add rollback support.

Automatically publish on tag.

Add pull and push support for relevant heads. This use pushkey.

Smarter states heads. We use the next relevant heads instead of repo one when asking for the head of a disabled state.

introduce a ``laststatewithout`` method We use it to remove explicite reference to state in to module code. This allow more flexible dev for now.

Autogenerate command table.

add templatekeyword in a proper location

Remove useless comment.

add dedicated command to mark changeset as published or ready This command coul be generated.

reorder extsetup

Get ride of dedicated heads property. This is now handle throught a generic repo.stateheads(state) methode.

rename state related attributes frozen is now published public is now ready

update doc

state are now object.

introduce a third state

stronger tests

Add write protocol support for private. Writeprotocol repo doesn't need to _reducehead locally. It's the heads command implementation server side that handle the filtering.

merge

fix clone

http test

fix test

hide private changeset to inc and pull.

Add "private" concept (2). private changeset are hiden suppose to be hidden for pull and push. For now it works for out and push

minimalistic state concept.