- Feb 10, 2013
-
-
kiilerix authored
-
- Feb 08, 2013
-
-
kiilerix authored
Bundle revisions had some info in their fake revlog intries and some info in a dict with all the bundle revisions. This dict was used to get the stored data and to distinguish repo revisions from bundle revisions. Real repo revisions and bundle revisions will now be distinguished by comparing with the tip revision of the original repo. This reintroduces something similar to disktiprev which was unused and removed in a928865b4a4f and let that replace the O(reposize) dict.
-
kiilerix authored
The display of nested lines for hg --profile was very non-obvious and made it look like sort didn't work. The '+' immediately before CallCount was not related to the CallCount and did not mean plus in any integer sense. The '+' before module looked like a part of the module name and not like ascii art. Instead we now indent the subordinate module names to clearly show the structure.
-
- Feb 10, 2013
-
-
durin42 authored
-
- Feb 09, 2013
-
-
Bryan O'Sullivan authored
We perform attribute dereferences and i18n lookups before looping.
-
Bryan O'Sullivan authored
This has a big effect on the performance of working dir updates. Here are the results of update from null to the given rev in several repos, on a Linux 3.2 system with 32 cores running ext4, with the progress extension enabled. repo rev plain parallel speedup hg 7068089c95a2 0.9 0.3 3 mozilla-central fe1600b22c77 42.8 7.7 5.5 linux-2.6 9ef4b770e069 31.4 4.9 6.4
-
Bryan O'Sullivan authored
If we estimate that it will be worth the cost, we run the function in multiple processes. Otherwise, we run it in-process. Children report progress to the parent through a pipe. Not yet implemented on Windows.
-
Bryan O'Sullivan authored
-
Bryan O'Sullivan authored
Not implemented for Windows yet.
-
Bryan O'Sullivan authored
This works on the major platforms, and falls back to a safe guess of 1 elsewhere.
-
Bryan O'Sullivan authored
-
Bryan O'Sullivan authored
Instead of a monotonic count, getupdates yields the number of files it has updated since it last reported, and its caller sums the numbers when updating progress. Once we run these updates in parallel, this will allow worker processes to report progress less often, reducing overhead.
-
Bryan O'Sullivan authored
In an upcoming patch, we will update .hgsubstate in a non-interactive worker process. Merges of subrepo contents will still need to occur in the master process (since they may be interactive), so we move that code into a place where it will always run in what will become the master process.
-
Bryan O'Sullivan authored
-
Bryan O'Sullivan authored
In a later patch, we'll run these updates in parallel.
-
Matt Mackall authored
-
- Feb 08, 2013
-
-
Kevin Bullock authored
Before this change, 'hg summary' would not show the active bookmark unless it pointed to the working directory parent. After this change, it will show it in parentheses, like so: parent: 18581:f0ff45fe6700 tip summary: simplify handling of active bookmark branch: default bookmarks: [crew] commit: (clean) update: (current)
-
- Jan 27, 2013
-
-
Kevin Bullock authored
-
- Feb 08, 2013
-
-
Kevin Bullock authored
This exposes the current behavior in a test. A later change will make summary show when the active bookmark has moved out from under us.
-
- Feb 09, 2013
-
-
Kevin Bullock authored
-
Kevin Bullock authored
-
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.
-
- 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
-