- Dec 08, 2017
-
-
Phil Cohen authored
We no longer inherit ``workingctx``'s version, but we also don't need to do anything anymore. Differential Revision: https://phab.mercurial-scm.org/D1239
-
Phil Cohen authored
Differential Revision: https://phab.mercurial-scm.org/D1238
-
Phil Cohen authored
Differential Revision: https://phab.mercurial-scm.org/D1249
-
Phil Cohen authored
Differential Revision: https://phab.mercurial-scm.org/D1248
-
Phil Cohen authored
Differential Revision: https://phab.mercurial-scm.org/D1247
-
Phil Cohen authored
Differential Revision: https://phab.mercurial-scm.org/D1246
-
Phil Cohen authored
Differential Revision: https://phab.mercurial-scm.org/D1245
-
Yuya Nishihara authored
-
Anton Shestakov authored
-
- Dec 07, 2017
-
-
Eamonn Kent authored
The fsmonitor extension should send state-enter and state-leave notifications to watchman when the wlock is acquired/release, respectively. This will allow watchman and watchman subscribers to customize behavior based on whether source control operations are occurring. Test Plan: Tested checkout, update and working copy changes with extension enabled. Differential Revision: https://phab.mercurial-scm.org/D1612
-
Eamonn Kent authored
Remove working copy change and transaction notifications. We were relying upon callbacks on transaction function. This caused issues with lock ordering. A different approach will be adopted in a subsequent commit. Differential Revision: https://phab.mercurial-scm.org/D1611
-
- Dec 08, 2017
-
-
Matthieu Laneuville authored
If operation is neither 'diff.inserted' or 'diff.deleted', label and token won't be define. This patch explicitely catches that exception.
-
Matthieu Laneuville authored
-
- Dec 06, 2017
-
-
Jörg Sonnenberger authored
Change the C implementation of phasecache.loadphaserevs to provide only the sets for draft and secret phase as well as the number of revisions seen. Change the pure Python implementation of the same functino to compute the sets instead of the list of phases for each revision. Change phasecache.phase to check the phase sets and assume public if the revision is in neither draft nor secret set. This is computationally slightly more expensive. Change phasecache.getrevset for public() based queries to compute the set of non-matching revisions and return the result as filtered fullreposet. A shortcut is taken when no draft or secret revision exists. Bump the module version for the changed interface contract. Overall, this saves around 16 Bytes per revision whenever the phasecache is used, for the test case in issue5691 it is around 3MB. getrevset() for a large repository is around 13% slower here, that seems an acceptable trade off. Performance impact for phase() should be similar. Differential Revision: https://phab.mercurial-scm.org/D1606
-
- Dec 08, 2017
-
-
Jörg Sonnenberger authored
Revisions are added consecutively, so a range can easily represent them in the changes list. This saves around 45 Bytes / revision on 64bit platforms and reduces the memory footprint of issue5691 by 15MB. Don't copy changes['revs'] in getobsoleted. Ranges have a very efficient contains implementation already. Differential Revision: https://phab.mercurial-scm.org/D1615
-
- Dec 06, 2017
-
-
Augie Fackler authored
This is a little risky, as I think we can have some encoding weirdness crop up. showfunc also isn't the most robust feature, but it's still often useful context... Differential Revision: https://phab.mercurial-scm.org/D1610
-
Augie Fackler authored
This was part of the original proposal, and while *I* don't like the curses interface, most users anecdotally seem to greatly prefer it to plain text interfaces. Differential Revision: https://phab.mercurial-scm.org/D1609
-
Boris Feld authored
This changeset make use of the ability of the set discovery to only search common changeset for a subset of the repository. Restricting that search to the pushed set avoid potential waste of time finding out the status of many unrelated related revision. Repository with many heads were especially badly affected by this. Here is an example of findcommonhead discovery for pushing 11 outgoing changeset on a repository with tens of thousand of unrelated heads. (discovery run over a ssh link to localhost). Before: queries: 92 time: 44.1996s After: queries: 3 time: 0.6938s A x63 speedup even with a network link without latency.
-
Boris Feld authored
Currently, the push discovery first determines the full set of common nodes before looking into what changesets are outgoing. When pushing a specific subset, this can lead to pathological situations where we search for the status of thousand of local heads that are unrelated to the requested pushes. To fix this, we need to teach the discovery to ignores part of the graph. Most of the necessary pieces were already in place. This changeset just makes them available to higher level API and tests them. Change actually impacting pushes are coming in a later changeset.
-
- Dec 07, 2017
-
-
Boris Feld authored
The extensions wrap the necessary function to ensure the 'largefiles' requirements won't be dropped. It is now possible to run `hg debugupgraderepo` on a repository with largefiles.
-
Boris Feld authored
Some requirement does not directly result from config and needs more advanced logic to be preserved. The current example is 'largefiles'. We add a hook point in the upgrade code so that extensions can handle these cases. The 'largefiles' extension will use it in the next changeset.
-
- Sep 22, 2016
-
-
Yuya Nishihara authored
This is the same behavior as ancestors(emptyset).
-
Yuya Nishihara authored
This seems natural given 'log -frREV' (with no file pattern) is equivalent to 'log -frREV *'.
-
Yuya Nishihara authored
Also renamed the argument from 'pattern' to 'file' conforming to followlines().
-
Yuya Nishihara authored
The diff might look slightly complicated, but the initial "c = repo['.']" was effective if rev = None.
-
Yuya Nishihara authored
-
- Oct 22, 2017
-
-
Yuya Nishihara authored
The original filectx API is kept public since we'll need it to walk ancestor (rev, match) pairs efficiently. The current implementation scans ancestors twice for 'hg log -fp FILE'.
-
- Dec 07, 2017
-
-
Phil Cohen authored
This is in preparation to switch this class to inheriting (and being based off a) `commitctx` instead of a `workingctx`. `filectx` has no `exists` function, so this is how we'll fall back in that case. Differential Revision: https://phab.mercurial-scm.org/D1237
-
Phil Cohen authored
Differential Revision: https://phab.mercurial-scm.org/D1236
-
Phil Cohen authored
We can no longer do so in the dirstate, so add the functions to do so here. Differential Revision: https://phab.mercurial-scm.org/D1235
-
Phil Cohen authored
Differential Revision: https://phab.mercurial-scm.org/D1234
-
Phil Cohen authored
Differential Revision: https://phab.mercurial-scm.org/D1233
-
Phil Cohen authored
In the future, the --inmemory flag might be deprecated in favor of something more intelligent (for example, always rebasing in-memory if the working copy parent isn't in the rebaseset). But we might keep it as a way to explicitly force IMM on or off. Differential Revision: https://phab.mercurial-scm.org/D1232
-
Phil Cohen authored
With rebase, we will be setting the _wrappedctx at a different point from the wctx construction (somewhat later, and possibly several times). Move it to a public function. Differential Revision: https://phab.mercurial-scm.org/D1231
-
Phil Cohen authored
Differential Revision: https://phab.mercurial-scm.org/D1214
-
- Oct 13, 2017
-
-
Jun Wu authored
This was intended to be done by D470. But there was a minor documentation issue. The feature is quite usable now so it gets formally documented and enabled. There is no behavior change for people not using the `SRC` or `ALLSRC` in rebase destination revset. .. feature:: Rebase with different destination per source revision Previously, rebase only supports one unique destination. Now ``SRC`` and ``ALLSRC`` can be used in rebase destination revset to precisely define destination per each individual source revision. For example, the following command could move some orphaned changesets to reasonable new places so they become no longer orphaned:: hg rebase -r 'orphan()-obsolete()' -d 'max((successors(max(roots(ALLSRC) & ::SRC)^)-obsolete())::)' Differential Revision: https://phab.mercurial-scm.org/D1063
-
- Dec 01, 2017
-
-
Phil Cohen authored
It will be called directly by rebase after concluding a node. Differential Revision: https://phab.mercurial-scm.org/D1230
-
Phil Cohen authored
Differential Revision: https://phab.mercurial-scm.org/D1216
-
Phil Cohen authored
Differential Revision: https://phab.mercurial-scm.org/D1215
-
Phil Cohen authored
Since D1105, these are unnecessary since IMM will now never use workers. Differential Revision: https://phab.mercurial-scm.org/D1213
-