1. Pierre-Yves David
  2. mutable-history

Commits

Show all
Author Commit Message Date Builds
Pierre-Yves David
evolve: update readme
Branches
stable
Pierre-Yves David
evolve: update tested with statement
Branches
stable
Pierre-Yves David
test: apply message changes introduced by mercurial 3.1
Branches
stable
Pierre-Yves David
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.
Branches
stable
Pierre-Yves David
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.
Pierre-Yves David
relocate: add transaction around phase movement cheap way to acces access to the transaction object
Pierre-Yves David
uncommit tr
Pierre-Yves David
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.
Pierre-Yves David
uncommit: saner locking scheme (and do it in the right order in the process)
Pierre-Yves David
prune: lock inside the try tss…
Pierre-Yves David
debugrecordpruneparents: release tr the same way than the lock Nicer code is nicer.
Pierre-Yves David
evolve: drop useless wlock in rewrite
Pierre-Yves David
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.
Pierre-Yves David
evolve: rename `tr` variable (for troubled) to `tro` tro is usually dedicated to transaction.
Pierre-Yves David
evolve: add a custom layer around retractboundary retract boundary is about to gain a new argument in core, we need somethign to handle this
Pierre-Yves David
merge with stable
Pierre-Yves David
evolve: point to the core mercurial tracker for bugfix As per Matt Mackall request evolution related bug should be filled again the main tracker as at some point al lof evolve wil be in core.
Branches
stable
Pierre-Yves David
evolve: drop reference to 2.3 in the extension help text We are far away from 2.3 now.
Branches
stable
Pierre-Yves David
readme: update the work in progress repository location
Branches
stable
Pierre-Yves David
readme: update the official documentation location
Branches
stable
Pierre-Yves David
evolve: deprecated --obsolete and --old-obsolete option on commit and graft Such option are unlikely to make it into core, so we deprecate them to avoid uer discovery them and getting used to them.
Pierre-Yves David
push: put phase in the same bundle2 than changegroup and obsmarkers Note that the usual phase push from core will be performed in all case. But the discovery should find already in sync phase at that time. The old ways sync will be properly skipped when this logic is introduced into core.
Pierre-Yves David
push: put obsmarkers in the same bundle2 than changeset When client is Mercurial 3.1 and server have proper evolve version and both side have bundle2 enabled, we'll includes a part containing obsolescence markers. When obsmarkers are included to the main bundle2 push, they will failed to be pushed if the changeset failed to be pushed (and reciprocally).
Pierre-Yves David
push: extract obsmarkers discovery in a dedicated function The need to factorise the computation of the markers to send in a dedicated function. This prepare the inclusion of obsmarkers in an atomic bundle2 push. For now, when obsmarkers are pushed using bundle2, they are still doing it on their own, in a dedicated bundle2 push.
Pierre-Yves David
evolve: update the tested with statement Tested with the soon to be release 3.1.
Pierre-Yves David
test: adapt to upstream message change A message gained parenthesis in 3.1 we reflect than in the test.
Nathan Goldbaum
uncommit: improve error message for use with no arguments
Pierre-Yves David
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.
Faheem Mitha
readme: mention patchbomb usage and patch description guidelines on wiki
Faheem Mitha
debian: add line to clean target to delete error files caused by failing tests
  1. Prev
  2. Next