1. Greg Ward
  2. mutable-history

Commits

Show all
Author Commit Message Date Builds
Greg Ward
docs: cover 'touch' command
Branches
default
Greg Ward
docs: explain that obsolete is not hidden
Branches
default
Greg Ward
docs: explain --hidden option Also move the discussion of revision numbers up, and splice the explanation of --hidden into it.
Branches
default
Greg Ward
docs: tweak wording, punctuation for better readability
Branches
default
Greg Ward
docs: flesh out unfinished bits in the intro page
Branches
default
Greg Ward
docs: revive the explanation of divergent changesets in the sharing guide
Branches
default
Greg Ward
docs (sharing): more scattered wording tweaks
Branches
default
Greg Ward
docs: sharing guide: clarify end-game of "Example 2" - push to dev-repo, rather than pulling into it (consistent with how we work the multiple developer scenario later) - explicitly demonstrate that public changesets are immutable
Branches
default
Greg Ward
docs: minor tweaks to sharing guide (suggested by timeless)
Branches
default
Greg Ward
docs: add code review scenario to sharing guide The idea is to demonstrate a simpler multiple-developer situation that does not involve getting into trouble. The final scenario illustrates Alice and Bob getting into trouble with bumped and divergent changesets by amending each other's history. The required tests and text are all written, but will need to be heavily revised because of the inserted scenario.
Branches
default
Greg Ward
docs: add a bit more hierarchy to the sharing guide
Branches
default
Greg Ward
docs: update sharing guide based (mostly) on marmoute's review - don't claim certain scenarios are more/less common, just simple/advanced - mention code review as a multiple-developer scenario (not described in detail yet!) - suggest "hg config --edit --local" instead of "cat >> .hg/hgrc" - use -q less often (and show resulting output) - edit some section headers to be consistent with user guide (example numbers; "amend" instead of "amending") (These a…
Branches
default
Pierre-Yves David
merge with stable
Branches
default
Pierre-Yves David
update readme
Pierre-Yves David
discovery: stop being stupid about variable name Overwritten variable are overwritten... The test coverage makes a simple pass in the loop :(
Pierre-Yves David
merge with stable
Branches
default
Pierre-Yves David
inhibit: explicitly test for None It is always better to check for None explicitly.
Branches
default
Pierre-Yves David
#iforgottoamendagain
Pierre-Yves David
discovery: port the new hashing version to simple4server
Pierre-Yves David
discovery: introduce a obshash1 function using fm1 during hashing (issue4587) The 'fm0' serialisation translate float to text. This give different result between python2.6 and python2.7 (because python2.7 got smarter). The 'fm1' is all binary and expected to be stable so we introduce the ability to do the discovery using hash computed with 'fm1' serialisation. We use a new wireprotocol version (Partly because I'm too lazy to check how to add an argument to the existing one…
Matt Harbison
tests: use 'wget' instead of 'curl' for Windows compatibility The whole test suite now runs without skips, and the only two failures are a bookmark cache issue in test-prune.t, and a local output vs remote output reordering when pushing to ssh. The latter anyway is a core problem.
DurhamG
setup: allow including inhibit in the build Adds the INCLUDE_INHIBIT environment variable to allow including the inhibit extension in the build.
Branches
default
Laurent Charignon
inhibit: Add -D option to the bookmark command The -D option for bookmark is similar to the -B option for strip. It deletes the bookmark and prunes the changes underneath it that are not reachable.
Branches
default
Laurent Charignon
inhibit: don't leave any obsolete commit visible after closing transaction We add a callback to wrap the transaction closure to identify commits that are obsolete and visible. We inhibit them to prevent the user to see instability in the UI.
Branches
default
Laurent Charignon
evolve: apply prune update before creating obsolescence markers Prune used to compute the destination commit to update to after creating the obsolescence markers. This is a commit to prevent a bug that would occur with the changes in inhibit for transactions (next commit). Indeed, with that change in inhibit, when creating the obsolescence markers in prune, they would get inhibited right away and we wouldn't update to the first non obsolete parent but stay on…
Branches
default
Pierre-Yves David
test-inhibit: check graph after prune We want to ensure prune keep working even with inhibit.
Branches
default
Pierre-Yves David
test-inhibit: drop trailing white space
Branches
default
Laurent Charignon
tests: make tests work on Mac OS wc -m adds spacing before the results, we trim them to make the test pass on Mac OS.
Branches
default
Pierre-Yves David
merge with stable
Branches
default
Laurent Charignon
inhibit: ensure that no obsolete changesets are visible after a bookmark change When creating a bookmark, we could reveal obsolete changesets. We are inhibiting the obsolete changesets resulting from a bookmark change. There are two ways to record bookmark changes to disk and we wrap both.
Branches
default
  1. Prev
  2. Next