- Dec 16, 2012
-
-
Mads Kiilerich authored
-
- Dec 12, 2012
-
-
Mads Kiilerich authored
-
- Jan 03, 2013
-
-
Pierre-Yves David authored
It does not have any user left
-
Pierre-Yves David authored
This prepare the dropping of the repo.hiddenrevs property
-
Pierre-Yves David authored
This prepare the dropping of the `repo.hiddenrevs` property
-
- Jan 08, 2013
-
-
Pierre-Yves David authored
If we are merging with and extinct revision, this extinct revision should not be hidden.
-
Pierre-Yves David authored
The `filteredrevs` function already have a cache mechanism. And this cache in invalidated at the same time than the current property cache. So we drop the cache on the property. The property itself is going to be dropped soon.
-
Pierre-Yves David authored
There is not good reason for this computation to be handle in a different way from the other. We are moving the computation of hidden revs in the filter function. In later changesets, code that access to `repo.hiddenrevs` will be updated and the property dropped.
-
Pierre-Yves David authored
[Should've been included in aff706b3a21c.] --Kevin Bullock <kbullock@ringworld.org>
-
- Jan 02, 2013
-
-
Pierre-Yves David authored
The `mutable` filter still have some chance to get invalidated. This will happen when: - you garbage collect hidden changeset, - public phase is moved backward, - something is changed in the filtering (this could be fixed) So we introduce an even more stable filtering set: everything with a revision number egal or higher than the first mutable changeset is filtered. The only official use of this filter is for branchcache.
-
Pierre-Yves David authored
It filters all mutable changesets, leaving only public changeset unfiltered. This filtering set is expected to be much more stable that the previous one as public changeset are unlikely to disapear. The only official use of this filter is for branchcache.
-
- Jan 07, 2013
-
-
kiilerix authored
Before: a symlink for python in BINDIR was sometimes created, but it was never updated when a different Python was used and it was never removed. An invalid python could thus be left around and used when testing with --local. Now: the symlink is removed when wrong and created when necessary. The mechanism for finding the right name (python or python.exe) also had to be simplified and made more explicit.
-
Pierre-Yves David authored
When log is not given the --hidden option, hidden revision are not shown. We move the implementation from manual checking at display time to changelog filtering. This is the first official usage of the hidden filtering.
-
Pierre-Yves David authored
This filter exclude all hidden revision. We plan to use this filter to hide revision instead of manually checking contents of the hidden revisions set.
-
- Jan 04, 2013
-
-
Pierre-Yves David authored
This helps when you focus on a subset of the volatile chain.
-
Pierre-Yves David authored
Obsolescence and filtering related caches are critical. Having a handy way to check them is valuable.
-
Pierre-Yves David authored
Some revsets are sensitive to such initialization. Being able to test the impact is great.
-
Pierre-Yves David authored
I'll add an argument to it.
-
Pierre-Yves David authored
Declaring synopsis and argument on the function site is much clearer.
-
Pierre-Yves David authored
The `perfnodelookup` lookup commands is duplicated. We drop the first version, overwritten by the seconds.
-
Pierre-Yves David authored
There is not reason to force passing of an empty options list.
-
- Jan 07, 2013
-
-
Pierre-Yves David authored
Filtered repository are *subset* of unfiltered repository. This means that a filtered branchmap could be use to compute the unfiltered version. And filtered version happen to be subset of each other: - "all() - unserved()" is a subset of "all() - hidden()" - "all() - hidden()" is a subset of "all()" This means that branchmap with "unfiltered" filter can be used as a base for "hidden" branchmap that itself could be used as a base for unfiltered branchmap. unserved < hidden < None This changeset implements this mechanism. If the on disk branchcache is not valid we use the branchcache of the nearest subset as base instead of computing it from scratch. Such fallback can be cascaded multiple time is necessary. Note that both "hidden" and "unserved" set are a bit volatile. We will add more stable filtering in next changesets. This changeset enables collaboration between no filtering and "unserved" filtering. Fixing performance regression introduced by 47f00b0de337
-
Pierre-Yves David authored
This will be used by branchmap collaboration. See inline documentation for more details
-
- Jan 02, 2013
-
-
Pierre-Yves David authored
If we want branchcache of different filter to collaborate, they need a simple way to copy each other. This will ensure that each filtered have no side effect on other filter level cache.
-
Pierre-Yves David authored
This will allows set operation needed for cache collaboration.
-
- Jan 07, 2013
-
-
kiilerix authored
Tests would wait for input instead of using non-interactive mode.
-
kiilerix authored
-
kiilerix authored
A bug introduced in 0c1d10351869 did that a part of the test never was run.
-
kiilerix authored
Mercurial would sometimes exit with: abort: No such file or directory where str of the actual OSError exception was the more helpful: [Errno 2] No such file or directory: '' The exception will now always show the filename and quote it: abort: No such file or directory: ''
-
- Jan 06, 2013
-
-
kiilerix authored
A line that should have been removed in 50fbe9063ff2.
-
- Jan 04, 2013
-
-
Kevin Bullock authored
-
Pierre-Yves David authored
When extensions had an empty `testedwith` attribute the code tried to parse it and failed. As a result the actual error were shallowed by a This crash. We now treat empty strip as 'unknown'
-
Pierre-Yves David authored
Branchcache of filtered version need up to date phase data.
-
- Jan 02, 2013
-
-
Pierre-Yves David authored
Disables this simple optimisation to allow coming more powerfull approach: cache collaboration. Our goal is to have branchcache collaborate. This means that unfiltered branchcache will fallback to some filtered branchcache if invalid. We can't have the filtered branchcache to use the unfiltered one. That would loop.
-
- Dec 21, 2012
-
-
Idan Kamara authored
When commit is followed by strip (qrefresh), phasecache contains nodes that were removed from the changelog. Since phasecache is filecached with .hg/store/phaseroots which doesn't change as a result of stripping, we have to filter it manually. If we don't write it immediately, the next time it is read from disk the nodes will be filtered again. That's what happened before, but there's no reason not to write it immediately. The change in test-keyword.t is caused by the above.
-
- Jan 04, 2013
-
-
Idan Kamara authored
We'd like the ability to call filterunknown on an existing phasecache instance after nodes are destroyed.
-
Pierre-Yves David authored
It iss dead code now.
-
Pierre-Yves David authored
Nobody overwrite the `_cacheabletip` any more. We always update the cache for the whole repo and write it to disk (or at list try to). The `updatecache` code is simplied to remove the double phase logic associated with _cacheabletip.
-
- Dec 28, 2012
-
-
Pierre-Yves David authored
Strip have dedicated work around to solve the same problem, strip is even a fraction faster without that thanks to simpler update process of the branchcache.
-
Pierre-Yves David authored
Now that bundlerepo use a read only VFS, we do not worry about what part of the branchmap is written back to disk. Nothing is written at all.
-