- Jan 30, 2013
-
-
Pierre-Yves David authored
We keep using a random seed for each run, but we "compute" it ourself to be able to reproduce a failed test run.
-
- Feb 09, 2013
-
-
Pierre-Yves David authored
If there is no outgoiing changesets but we have filtered revision in outgoing.excluded We run into a filtering related crash. The excluded revision should not be there in the first place but discovery need cleanup in default, not stable.
-
durin42 authored
-
durin42 authored
This violated user expectation. Updated the code to clobber files, but preserve the behavior of appending multiple patches requested in a single export. Includes tests.
-
Bryan O'Sullivan authored
This reduces the amount of time we spend calculating when doing a clean non-merge update. In a large repo, the time dropped from 10.1 seconds to 3.4.
-
Bryan O'Sullivan authored
This is always a workingctx, and this name is more in line with other functions in this module.
-
Na'Tosha Bard authored
-
- Aug 03, 2013
-
-
Simon Heimberg authored
Using only one message makes live easier for translators. The clearer error message was supposed by Augie Fackler.
-
Simon Heimberg authored
Editing the history only is possible when the working dir is a descendant of the revisions to edit. When this happens explain it by writing abort: %s is not an ancestor of working directory
-
- Feb 09, 2013
-
-
Bryan O'Sullivan authored
-
Siddharth Agarwal authored
This replaces the _checkunknown call in calculateupdates with a more performant version. On a repository with over 150,000 files, this speeds up an update by 0.6-0.8 seconds, which is up to 25%. This does not introduce any UI changes. There is existing test coverage for every case, mostly in test-merge*.t.
-
- Feb 08, 2013
-
-
Siddharth Agarwal authored
This will be used in an upcoming patch.
-
- Feb 09, 2013
-
-
Siddharth Agarwal authored
Previously, the manifest cache would store the last manifest parsed. We could run into situations with operations like update where we would try parsing the manifest for a revision r1, then r2, then r1 again. This increases the cache size to 3 to avoid that bit of performance fragility.
-
Siddharth Agarwal authored
In certain cases we would like to have a cache of the last N results of a given computation, where N is small. This will be used in an upcoming patch to increase the size of the manifest cache from 1 to 3.
-
Kevin Bullock authored
Removes the last of the warnings in test-check-code-hg.t introduced in 667063b22a69.
-
Kevin Bullock authored
If obsolete markers appear in the hg repo (because of enabling evolve), then tests that run hg against the hg repo itself will see warnings like: obsolete feature not enabled but 4 markers found! As far as I can tell, this only occurs in test-check-code-hg.t -- in particular, it will -not- show up on tests that run against test-created repos, as most of the test suite does.
-
Na'Tosha Bard authored
In some cases, caching largefiles may take a long time (if the user has pulled a lot of new heads). This patch makes it more clear what is happening, by showing the number of heads we are caching largefiles for.
-
Na'Tosha Bard authored
-
Benoit Boissinot authored
-
durin42 authored
-
durin42 authored
-
durin42 authored
-
durin42 authored
-
durin42 authored
-
durin42 authored
-
durin42 authored
-
durin42 authored
-
durin42 authored
-
durin42 authored
-
durin42 authored
The non-hexlified node was leaking all the way out to the web interface, and wasn't consistent with the behavior for nonexistent nodes.
-
- Feb 08, 2013
-
-
durin42 authored
We don't care about the original traceback, and this was frustrating any efforts to make the code work on Python 3.3.
-
- Feb 09, 2013
-
-
Benoit Boissinot authored
-
Kevin Bullock authored
-
Kevin Bullock authored
-
- Feb 08, 2013
-
-
Benoit Boissinot authored
-
Benoit Boissinot authored
Currently only useful with the json filter.
-
Matt Mackall authored
-
Matt Mackall authored
-
- Feb 05, 2013
-
-
Arne Babenhauserheide authored
Use e for edit instead.
-