readme: drop the reference to fastobs Its dead Jim.

merge with stable

Added tag 3.3.1 for changeset fc04758ea9f5

prepare release 3.3.1

fix maintainer email I'm not working at Logilab since july 2013. Using my personal address to prevent this kind of situation in the future.

fold: enable --date and --user options Like all other commit-creating commits, `hg fold` should also have these options enabled. This also allows getting consistent hashes during tests involving fold.

evolve: improves readme wording (yes I just pushed the other version…)

evolve: update changelog in README

test: update testing statement

evolve: abort when trying to move a node on top of itself This provides a clearer error message when evolve misstakenly tries to move a changeset on top of itself. Before we got an abort with a cryptic message about trying to rebase a merge changeset. A proper fix to make sure that evolve never tries to move a node on top of itself will come in later patches.

run-tests: add executable bit

rewrite: use cmdutil.logmessage instead of ad-hoc methods The logic for handling the --message and --logfile options is already in core hg in the cmdutil.logmessage function. This patch removes this duplicate logic from Evolve and just calls the core function.

fold: enable --date and --user options Like all other commit-creating commits, `hg fold` should also have these options enabled. This also allows getting consistent hashes during tests involving fold.

merge with stable

test: sort output of listkey command The pushkey namespace came as dict key. So they have no defined order. We sort them to stabilize the test.

exchange: use fixed order for obstore content The obsstore content seems unstable from one version of python to another (we most certainly use some dict) we fix the order once and for all.

Finish killing fastobs (this test failed loudly after 33fdaec24432)

Kill fastobs, as marmoute says it causes problems

tests: fix test-prune.t breakage test-prune.t was broken due to 91d28bd0e04e in upstream Mercurial, which made hidden commits visible when a local tag made the commit reachable. The fix is to delete the tag in the test.

Fix preservation of rename information on evolve (#33) Following what rebase itself does, call duplicatecopies between rebasenode and concludenode. Should fix https://bitbucket.org/marmoute/mutable-history/issue/33/evolve-command-loses-copy-metadata

merge stable into default

tests: fix test-prune.t breakage test-prune.t was broken due to 91d28bd0e04e in upstream Mercurial, which made hidden commits visible when a local tag made the commit reachable. The fix is to delete the tag in the test.

evolve: small white space change

evolve: use new api _callcompressable This changeset makes evolve compatible with the change introduced in 167047ba3cfa

evolve: downcase first word in module doc This makes the output of hg help consistent with the other extensions.

evolve: deprecate gup and gdown aliases This is done in an effort to clean up the UI of evolve.

evolve: add function to deprecate an alias When cleaning up the UI for evolve we will deprecate old aliases, but still want them to work for a while. This is a helper function that will be called during the extension setup and has the ability map an old alias to a new or canonical one.

evolve: downcase first word in module doc This makes the output of hg help consistent with the other extensions.

evolve: active bookmark should move when using prev/next (#37) The #37 references the bitbucket issue for mutable-history, that can be found here: https://bitbucket.org/marmoute/mutable-history/issue/37/

commands: small language fixes in help

evolve: abort when trying to move a node on top of itself This provides a clearer error message when evolve misstakenly tries to move a changeset on top of itself. Before we got an abort with a cryptic message about trying to rebase a merge changeset. A proper fix to make sure that evolve never tries to move a node on top of itself will come in later patches.

run-tests: add executable bit

evolve: add a hook related to the new pushobsmarkers command Before the current expericment, people could hook on obsolescence marker push using pushkey. We add a new hook to serve the same purpose.

exchange: dropping dead code (issue36) This variable does not exist anywhere else in the code.

evolve: fix evolve with mercurial default MODERNCAPS have been renamed to moderncaps upstream.

simple4server: update tests Forgot to amend before pushing.

sinmple4server: advertise new cap only when advertising obsolescence This is more consistent.

evolve: do not exchange obsolescence markers when server refuse it The server can be configured to refuse obsolescence markers exchange. See changeset 48804a8d7472 for details about it. We respect server will in the client.

simple4server: option to advertise obsolescence support We had an option to control the advertising of the obsolescence markers support from the server. The goal of this option is to allow large scale repo hosting service to control the use of obsolescence markers exchange.

export: add test for simple4server We now officially test it over http

exchange: fix push markers over wire protocol for http peer Http actually interpret the data passed to _callpush expecting them to a bundle. Interpretation of a markers stream as a bundle obviously led to crash.

exchange: expose length of pushed markers http wireprotocol will need it.

simple4server: update "from <changeset>" statement Could obviously not do it in the same changeset than the original changes.

exchange: fix changeset pulling over http http compress its stream. The were building a bogus stream where the first 10 bytes where uncompressed. Confusing the client.

simple4server: update "from <changeset>" statement Could obviously not do it in the same changeset than the original changes.

exchange: properly wrap wireprotocol capabilities Just wrapping the module function only works for ssh. Ssh gets capability through the `hello` command. We also need to wrap the function stored in the command dict. This fix discovery for http peer.

simple4server: add origin and documentation to most function

evolve: add 2.9.1 compatibility seal to simple4server

simple4server: fix a missing import

evolve: update version compatibility error message

exchange: fix pull over wire protocol Actually hand pulled obsolescence markers to the pull logic. In the wire protocol case we did not reset the position of the file pointer after writing the pulled data. This lead the pull logic to thing that no markers were send at all. This changeset fix this client side bug. (apparently no test check both markers pulling and wireprotocol)

exchange: enforce permission on new wireprotocol command hgweb needs an explicit declaration of the permission level of each commands.

merge stable

evolve: fix typos in uncommit docstring

simple4server: add the wireproto command for obsolescence markers discovery This come with its usual train of duplicated utility.

discovery: use the discovery process for pull Wow! Such speed! Much functional! Very proof on concept implementation!

discovery: implement a discovery process and use it for push Much faster! So functional! Very proof on concept implementation! Wow!

discovery: first version of the "hash tree" idea We build a hash for each node based on the markers that applies to it and the hash of its parent. This will allow a kind of discovery process for markers.

evolve: update changelog with recent advance

merged 3.3 release into default Some of the default content was released in 3.3.0 the other ones are moved to 3.4

Added tag 3.3.0 for changeset 83882f2fbecb

prepare 3.3.0 release

evolve: drop `latercomer` and `conflicting` compatibility. Those old alias are deprecated for a long time now. All computations related to troubles are in Mercurial core for multiple versions.

evolve: use flag value from core for bumped fix This flag is available from core for a long time, lets use it directly from there. This commit intend to cleanup old stuff from the evolve extention.

test: get rid of all reference to conflicting changesets They are now called divergent for a long time.

merge various improvement to stable We want a good stable state before starting massive changes in default for obsolescence marker update.

exchange: add progress bar when pushing using wire protocol command Progress bar on pull was only available for pushkey based push before this changeset. This implementation is very hacky but we are still at a proof of concept stage for those new exchange method.

exchange: add progress bar when pulling using wire protocol command progress bar on pull was only available for pushkey based pull before this changeset.

exchange: fix pulling from simple for server There is far too much code duplication down there.

exchange: add test case for D.4

exchange: add test case for D.3

exchange: add test case for D.2

exchange: add test case for D.1

exchange: add test case for C.4

exchange: add test case for C.3

exchange: add test case for C.2

exchange: add test case for C.1

exchange: add test case for B.7

exchange: add test case for B.6

exchange: add test case for B.5

exchange: add test case for B.4

exchange: add test case for B.3

exchange: add test case for B.2

exchange: add test case for B.1

exchange: add test case for A.7

exchange: add test case for A.6

exchange: add test case for A.5

exchange: add test case for A.4

exchange: add test case for A.3 Allow arbitrary arguments to dotest. This allow to push --force when the push creates more heads.

exchange: automate the testing process too we now have: dotest TESTNAME [TARGETNODE]

exchange: have a function doing all the common initial setup This will help creation of further test.

exchance: add a common setup script for all test

exchange: add test case for A.2 Testcase defined here: http://mercurial.selenic.com/wiki/ObsolescenceMarkersExchange

exchange: add test case for A.1 Testcase defined here: http://mercurial.selenic.com/wiki/ObsolescenceMarkersExchange

exchange: add the pullmarker wireproto command to simple4server This will allow simple server side support. (yes, code duplication is bad I already told you I won't do it too much mom)

exchange: extract computation of pulled markers boundary in a function I expect massive experimentation on this specific aspect. so we better isolate it.

exchange: pull markers relevant to the pulled subset only With the command recently introduced we can select to pull only markers relevant to some nodes. We are now pull all markers for all node in the relevant subset. We'll try to pull less (just markers for node where local and remote marker diverge) later, but we need some marker discovery mechanism for that. which are not easy.

exchange: add a new method to pull markers It has both local and wire protocol implementation. This command does not requires escaping of the marker and are expecting to me highly faster than the pushkey method. The other main point is that command is to accept a `heads` and `common` argument to select to pull changeset only relevant to a set a of node. We are not using this capability yet but we'll do it soon

exchange: add the pushmarker wireproto command to simple4server This will allow simple server side support. (yes, code duplication is bad, I won't do it too much mom)

exchange: introduce a wireprotocol command to push markers Pushkey is not adapted to transmit a stream of binary data. We used it as a hack so far. We add a new wire protocol command to speed the things up (and also push all the markers in a single transaction). The proper way to do it is to introduce bundle2 in core, but this will already help in the mean time.

exchange: actually use _pushkeyescape fallback The code was still calling `obsolete._pushkeyescape` therefore never calling the fallback we defined. Now that we call it, it had to be fixed to actually work too.

merge with stable

prune: accept '0 0' as a valide --date value I 've no idea why 4c0f6d555032 introduced it with this check.

exchange: only push the set of marker relevant to want we push We now compute all markers relevant to pushed set. And just send just those one. So you are no longer pushing markers that point to changeset your are not pushing. See the in line comment for details about what "relevant" is. Multiple nice output have been added in the process.

evolve: add relevant marker exchange machinery This is going to be needed for obsolescence marker exchange.

fastobs: rename var from `node` to `rev` It contains revision (from repo.revs not node).

fastobs: move the extension to the hgext dir

test-prune: update test with a prune output compatible with newest hg Newest hg can record the parent information in the marker. This change the debugobsstorestate output a lot.

drophack: major speedup to marker stripping It appear that each call to obsstore.add have a significant overhead (in particular the creation of a set form the list of markers and file system operation to the obsstore file. We now compute the marker we need to store and write them in a single call.

evolve: add a cmddebugrecordpruneparents command This command can be used to create prune marker with parent information from prune marker on changeset known locally.

debugobsstorestat: add test for pruning There is multiple prune specific code in this command. So we test it in the presence of prun marker too.

debugobsstorestat: add information about cluster We now display information about independant osolescence markers clusters.

evolve: fix creation of prunedchildren for merge The `p2` code path was broken. (stupid typo)

evolve: add a debugobsstorestat command This commands print multiple some data about the content of the obsstore. This will be usefull to provide some metric and insight for obsolescence marker exchange.

evolve: extend obsstore object to use prune parent information Now that we have the information, we can use it to build a mapping to access all marker that prune a children of a node. This is similar to what we do for successors and precursors. The performance impact is a few tens of second on my mercurial clone. Experimenting is worth the trouble.

prune: wrap mercurial internal to add parent information in prune marker We store as a p1 (and p2) key in the extra dict for marker. This allow us to record this information for future use without requiering a format change.

evolve: drop `latercomer` and `conflicting` compatibility. Those old alias are deprecated for a long time now. All computations related to troubles are in Mercurial core for multiple versions.

test: get rid of all reference to conflicting changesets They are now called divergent for a long time.

evolve: use flag value from core for bumped fix This flag is available from core for a long time, lets use it directly from there. This commit intend to cleanup old stuff from the evolve extention.

importing fastop extension in this repo This repo is dedicated to experimentation on mutable history topic. Fastop is appropriate there.

fastobs: revset refactor related fixes

adapt fastopt extension to mercurial.exchange module The push code have changed to be more modular. the fastop extension need to be rewritten. No backward compatibility preserved for mercurial <=2.9x.

drop unused function `pushmarkerwrapper` I can find any user for this function.

Add initial test.

Deduplicate markers. Depends on __hash__ and __eq__ on obsolete.marker

copy precursor revset from evolve so we don't depend on involve

fastobs: details strategies in the main help

fastobs: fix a bunch of stupid errors that prevented it from working at all

fastobs: clean up logging a little

fastobs: first commit of an extension to test obsolete marker exchange methods This currently implements the "fill in the box" approach discussed at the 2.6 sprint, which seems to handle common cases correctly with significantly less data transferred.

drophack: add a new drop hack extension for Matt Mackall usage This extension is hacky and not intended for real world usage. See documentation for details.

prune: add biject option This option allows two ranges to be given for successors and precursors such that there is a one-to-one match between each range. Test coverage has been added.

evolve: register a summary hook instead of wrapping the summary command

merge stable into default.

doc: improve reference to log --hidden - glog is not mucha thing anymore - also add a usage exemple

doc: fix trailing white space

doc: DIE MQ DIE

doc: use --succ in prune help --succ is the new only way.

doc: remove referenc to proleferation of hidden commit This is not much something we try to avoid anymore This changeset is eathenly adding reference to other toubles too.

doc: try to clarify rebase warning

doc: enhance your fold help Refer to the two different for of using fold.

doc: refer to previous and next in the gup, gdown help

doc: replace graft -O with grab

doc: rework how to entry about amend We can recommand the core `hg commit --amend` now. We also drop reference to MQ.

raise util.Abort instead of assertion when trying to evolve a merge changeset. This prevent exposing a nasty traceback to the user.

merge with stable

tutorial: fix note We need a double semin colon, otherwise this is a comment.

tutorial: warn about rollback beeing obsolete

tutorial: use grab instead of rebase. grab as now the advantage to move the working directory.

tutorial Clarify "." explanation

tutorial: update divergent changeset section Still not there but less fuzy.

tutorial: use long form of argument for the sake of clarity

tutorial: fix some various typo

tutorial Display the help of appropriate command in section that need writting

doc: some documentation on the configuration part of the tutorial Trying to make it less obscure on first contact

doc: smarter make file We regenerate the tutorials when needed only

doc: use a symbolic link to point to the tutorial the file was lagging behind a ton.

import: warn about new unstable changesets 'hg import' can add new unstable changesets, for example when invoked with '--hidden' or '--exact', or when the working directory parent already is unstable.

evolve: show progress The total count may be too low on occasion. Not sure why. gaved up at testing this, can't get stable result.

removed the qsync extension. The only user I knew about (logilab) is not using it anymore. It not compatible with coming Mercurial version 2.9.

evolve: add more details when we abort for case not handled yet Verboser output to help people knowing what is going on and solving it on their own.

merge stable back into default

current release is stable enought

evolve: update the tested with statement It actually ssems to work with version up to 2.6 but some minor changes makes test fails. so better encourage people to upgrade.

evolve: use super for calling parent class method Otherwise we can bipass filtering (and break a lot of things)

debian: add source/format file

Added tag 3.2.0 for changeset c3ba8a965a7a

prepare 2.8 release

grab: update the alias for 2.8 compatibility 2.8 does not update on rebase anymore. We need to update by hand. this makes this alias more fragile.

gdown/gup: add next/previous alias Up and down refer to the customary order in log output rather than concepts; as such, it may be confusing to the user. I for one found them suprising -- they just didn't fit with my mental model. Previous and next, however, imply a clear parent/child relationship. We attroduce the new name as aliases for now.

evolve: allow updating to the successor if the parent is obsolete Although 'hg update' handles this as well, it will also update to tipmost descendent of the successor, if any.

evolve: abort on unknown divergent changeset base ...rather than noisily dying with a KeyError.

test: prepare test for core changeset 6cd9b8428104 Changeset 6cd9b8428104 in Mercurial core (2.8) make rebase preserve more extra. this mean hash changes. We make the test resilient to that.

test: prepare test for core changeset 9c78ed396075 New changeset in mercurial 2.8 (9c78ed396075) change rebase behavior to preverse the original working directory. This break an handfull of test so we preventively update to tip after rebase.

merge stable into default

add obsolete parents wrapper to the 'parents' command although the command itself cannot *cause* obsolete changesets, the information is rather relevant to the state of the parents

README: update changelog

conform to the Mercurial custom of lowercase messages ...and while at it, use the more usual long form of "can't"

amend: use core mechanism for amend Evolve used its own code for amending. This was introduced before mercurial includes commit --amend. The evolve code is now older and buggier. So we just use the core cod when amend is called. Message of the temporary commit is different, all test hash changed \o/. Test change are been carefully checked.

amend: drop the deprecated note option We plan to get closer to the commit --amend implementation dropping this deprecated option helps.

test: adapt to 2.6 message improvement From fd1bb7c1be78 (in core) hidden revision are excluded from partial match in a proper way resulting in a nicer error message.

README: polish the language so it reads better

README: fix spelling, capitalization, grammar, punctuation

README: fix minor markup inconsistencies

3.2.0

debian: properly clean the docs build

pushexperiment requires mercurial 2.6

ship pushexperiment extension

pushexperiment: guard against non-push-capable remotes

pushexperiment: fix doc typos

merge stable into default

push obsolescence marker before anything else

add notification at the end of push We have a dedicated hook to know when a push is done.

Add a new pushexperiment extension This extension introduce a faster way to push obsolescence marker. Send the obsstore directly instead of inefficiently going through pushkey's inefficiency.

Adapt to human readable date in patch

debian: honor nocheck in DEB_BUILD_OPTIONS

evolve: fix typo

amend: hide the --note option The intermediate commit will not survive long

evolve: remove trailing spaces

update debian changelog

merge with stable

Added tag 3.1.0 for changeset cdb52bbbe5b8

evolve: update test output.

prepare release 3.1.0

prune: add --user and --date options They control the metadata writen to the obsolescence marker.

prune: add strip-like bookmark This prune changesets pointed by the specified bookmark only (and removes the bookmarks)

evolve: remove duplicate alias.

evolve: update stabilize order test after output change

merge with stable

evolve: document --all option

merge --all option from tak

minor help changes

evolve: clean up help message

evolve: remove magic return values from utility functions

evolve: clean up evolve implementation.

evolve: add test for evolve --all.

evolve: add --all argument.

evolve: extract evolve --any implementation into a function.

touch: properly handle touching multiple changeset

add a duplicate option in touch

touch: add basic testing

amend: prune replacement commit without sucessors This align with the core behavior of `commit --amend`. All user of rewrite are not responsible for creating their own marker.

changelog: add more entry

fix future 3.1.0 changelog entry

alias: add a grab alias Its a valid replacement for graft -O

amend: drop the --change option it is deprecated for quite some time already

drop suspicious import in evolve introduced by 97ce1f801309 Thanks to Bryan Murdock for reporting the issue.

prune: handle bookmark

test-prune: simplified log output useful to testing bookmark later

prune: update inline documentation

prune: more command switch idea

prune: documentation update

prune: add an informative message about the number of pruned changesets

prune: test and improve message of immutable aborting.

prune: turn one of the test changeset public

prune: add test and more robusness

prune: detect bad input We accept multiple changeset folded into one successors. One changesets split in multiple successors. But we refuse multiple changesets split in multiple ones.

simplify locking in prune

prune: rename --new to --succ This is closer to want the documentation says.

prune: improve command function name

prune: fix doc

evolve: drop uneeded noderange function We can use revrange instead

evolve: warn for troubles created by histedit too.

drop useless empty lines

evolve: remove outdated documentation

add an explicite warning when repo contains invalid obsolescence markers

evolve: remove pre 2.3 code

evolve: removes amend from the list of advertised function We have commit --amend almost as powerful now.

evolve: fix extsetup extension helper

evolve: remove unused function imported from mercurial

evolve: drop unused import

merge with doc fixes

merge with stable

doc: update version information

merge with hg2.4 compat branch

Added tag 3.0.0 for changeset 862b6b71a358

prepare for release 3.0.0

mark test with 2.5

merge

create a compat-hg2.4 branch 2.5 is out, 2.4 compatible code is parked in a compat-hg2.4 branch as we did for 2.3

hgext: add a simpler extension to enable obsolete on server

drop: divergence related code It is now in code

evolve: remove revset calls in warnobserror revset have serious performance impact in several case. The resulting code is a bit too complicated to my taste. I hope for much simpler implementation in core anyway.

evolve: drop "troubles" and "troubled" method now in core

test: drop rebase test We assume that the mercurial rebases tests suite is strong enough now.

doc: fix grammar, spelling, punctuation I restrained myself to making only changes that turn bad English into good English. There are still opportunities to improve, but other changes require some discussion and review. This change should be uncontroversial.

tutorial: fix grammar, spelling, punctuation I restrained myself to making only changes that turn bad English into good English. There are still opportunities to improve the tutorial, but other changes require some discussion and review. This change should be uncontroversial. The same changes had to be duplicated in both copies of the tutorial (hmmm); it's not clear which one is definitive.

[evolve] Drop useless filtered code

merge with filtering change (DO NOT USE WITHOUT FILTERING)

evolve: ensure evolve command run unfiltered

test: drop divergent test It is into core now

evolve: stop working around phase limitation Core is handling this part a bit better

fix punctuation

evolve: fix version message

test: more resistance to filtering changes

merge with stable

support -r option in prune, add a test for this Also localize options in fold.

doc: index version info on index

doc: updates mq refugee book

doc: update how-to

tutorial: second replacement of hg amend by commit --amend (the diff is huge because commit --amend have protection vs cycle)

tutorial: use evolve directly We a real mode in addition to the dry run one.

tutorial: use rebase instead of graft -O

tutorial: use commit --amend when possible commit --amend is the core way to do that, we better get used to it.

evolve: make evolve smarter It is not more confused by killed changeset and can also choose to stabilise '.'

tutorial: update notes in unwritten section

tutorial: glog is into core now

test: adapt to the way the bundle is generated optimised generation gives 1 changes, strict on gives 2.

fold: work around potential bug with filtering Folded revision may be becomes filtered leading to a crash of the replaced rset.

prepare for filtering

compat: adapt to upstreaming of divergent logic successorsset and divergent logic have been moved into core by changeset 4bec77e62c00::e411fd79ca69 We drop dedicated code in evolve.

Added tag 2.1.0 for changeset f9d305deeff3

[prepare] 2.1.0

update changelog

merge with fix in 2.3

prepare for Full scale filtering !!!

more versatile test. push can fails on any divergent changeset I do not care for now.

fix retrieval of divergent changesets in obssummary (typo) Add a test for this; drop wrong divergent print in 'Test rollback support'.

merge with Denis improvement

merge with Denis improvement

use comments to combine commit messages in fold

add a -e option to fold

merge

detect incompatibility with future mercurial 2.5 changes in bookmark break compatibility

merge

merge

Added tag 1.1.0 for changeset 22cacfce2a65

fix version in setup.py

adapt to 7f5dab94e48c in crew

deprecate "amend --change" option

merge with qsync fix

merge with qsync fix

merge with qsync fix

[qsync] fix filestore usage The filestore was closed too early, dropping on disk cache

merge back with stable

Added tag 2.0.0 for changeset d43e80504e5

evolve: some comment update Bumped is in core now.

update debian control

merge 2.4 code back into default.

merge with 1.1.0

Added tag 1.1.0 for changeset c062edbcaf13

Fix debian control

prepare a branch for Compat with mercurial 2.3 only

prepares evolve 1.1.0

merge changelog update

update changelog with future 1.1.0 news

merge bumped rename (drop several part of the code because bumped is now in core)

evolve: Rename latecomer into bumped This is the new name in core

evolve: set tested with 2.4

evolve: require Mercurial 2.4 to work

evolve: adapt to 2.4 code

merge with stable

mercurial: replace all `newerversion` call by `successorsset` call

evolve: smarter code for divergent changeset This newer version properly handle split now. Code and test copied for future upstream one.

evolve: rename conflicting into divergent

evolve: detect and abort if 2.4 is detected The meaning of critical attribut have changed in 2.4

evolve: add tested with info

merge stable into default

test-stabilize-conflict.t: fix "eight" spelling

test-stabilize-conflict.t: sed -i is still not portable

test-stabilize-conflict.t: yes is not a standard shell utility And for some reason the test fails on OSX.

evolve: drop code now in core The default branch aims compat with the mercurial default branch. we do not need all those conditional.

merge with default

evolve: filter nullid successors

evolve: new divergent revset

doc: rename conflicting to divergent.

more schema

merge stable into default

adapt to core rebase support

rebase: warn about troubles created by rebase The previous order created obsolete marker after checking for new troubles

test-obsolete: clean up useless inlined option rebase is enabled globally and graphlog is into core

add image magic depends

upgrade debian changelog

update MANIFEST.in

merge (overwrite wrong tag)

Added tag 1.0.2 for changeset 5559e5a4b656

prepare 1.0.2

Added tag 1.0.2 for changeset b1bdcb4506de

hg prune: prevent empty call

fold: handle the lack of revision to fold

fix readme header

slight change to the evolve logo thank to Adrien Di Mascio

docs: fix makefile

doc: add a logo It's not that cute be we have one.

README: remove bogus date This version is not released yet.

update changelog

commit --amend: adap to core 63e45aee46d4 commit is now able to create obsolete marker itself. We don't alter core if we detect it's the case.

createmarkers: adapt to f85816af6294 in core The createmarkers function is now in core. Fallback on our function if not available

warning: work around phase limitation when computing warnings The new phase have not been written yet because we did not release the lock yet :-/

caches: now in core adapt to fb72eec7efd8 If we detect a cache mechanism in core we is it intead of instead our own

evolve-cmd: fix merge error detection for external tools.

Properly update after fold The previous version only set the parent, it did not rebuilt dirstate or update any file content.

fix hg pull --rebase There is more user of rebase than just the rebase command

remove all notion of --detach in the test Mercurial 2.3 killed --detach (dance)

fix missing --dest evolve output in dryrun

pkg: proper debian version

pkg: debian changelog

Added tag 1.0.1 for changeset ca5bb72d14ae

pkg: abstract version in makefile

pkg: prepare version 1.0.1

evolve: fixing syntax/grammar

hgweb: disable branchtip filtering for hgweb hgweb make extensibe use of branchtip we should. - Our branchtip wrapping make the function expensive, killing performance. - We do not filter anything un hgweb yet.

doc improvement

pkg-debian: fix uploader fields

pkg-debian: improve control files

pkg-debian: remove conflicting __init__.py files

a better msg for this tricky situation

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"