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