- Nov 01, 2017
-
-
Augie Fackler authored
-
Wagner Bruna authored
-
Matt Harbison authored
-
- Oct 31, 2017
-
-
Yuya Nishihara authored
The original condition was a bit harsh for extension authors since third-party extensions need to preserve compatibility with older Mercurial versions, where no defaults would be loaded from the configtable. So let's silence the warning if the given default value matches, which should be harmless.
-
- Oct 26, 2017
-
-
Kostia Balytskyi authored
After a refactoring, _toolstr stopped having default="" as one of it's args, therefore when called without a default it returns None and not "". This causes concatenation to fail.
-
- Oct 31, 2017
-
-
Pulkit Goyal authored
`hg log -r children()` returns `hg: parse error: missing argument`. Differential Revision: https://phab.mercurial-scm.org/D1269
-
- Oct 29, 2017
-
-
Yuya Nishihara authored
It appears that stderr is fully buffered on Windows. # no-check-commit because of log_message() function
-
- Oct 28, 2017
-
-
Yuya Nishihara authored
It wouldn't work between Windows client and Unix server.
-
- Oct 24, 2017
-
-
Siddharth Agarwal authored
We shouldn't ship a severe perf regression in hg update for 4.4. Differential Revision: https://phab.mercurial-scm.org/D1223
-
Siddharth Agarwal authored
We've found a severe perf regression in `hg update` caused by the path conflict checking code. The next patch will disable this by default. Differential Revision: https://phab.mercurial-scm.org/D1222
-
- Oct 20, 2017
-
-
Mark Thomas authored
When a dirstate backup is restored, it is possible that no actual changes to the dirstate have been made. In this case, the backup is still a hardlink to the original dirstate. Unfortunately, `os.rename` silently fails (nothing happens, and no error occurs) when `src` and `dst` are hardlinks to the same file. As a result, the backup is left lying around. Over time, these files accumulate. When restoring dirstate backups, check if the backup and the dirstate are the same file, and if so, just delete the backup. Differential Revision: https://phab.mercurial-scm.org/D1201
-
Mark Thomas authored
Differential Revision: https://phab.mercurial-scm.org/D1200
-
- Oct 21, 2017
-
-
Matt Harbison authored
I'm not sure why these weren't working on Windows. The failures were generally in the style of: - remote: phase-move: cb9a9f314b8b07ba71012fcdbc544b5a4d82ff5b: 1 -> 0 + remote: "phase-move: $HG_NODE: $HG_OLDPHASE -> $HG_PHASE" and - abort: pretxnclose-bookmark.force-forward hook exited with status 1 - [255] + abort: pretxnclose-bookmark.force-public hook exited with status 255 + [255] These failures originated in ee5f0d047b41::f6d17075608f.
-
Matt Harbison authored
The '\n' characters were being translated on Windows, throwing off hg and git hashes, as well as the file content in the diff.
-
- Oct 20, 2017
-
-
Matt Harbison authored
Previously, the second last test (context.arbitraryfilectx(..)) returned True on Windows. I changed the repo setup sequence to import a patch, so that way the repo would have a proper symlink. That made the last test fail, since it is comparing files in wdir(), one of which is not the expected symlink. Apparently the (feature !) line matching doesn't work well with (no-eol), so I had to conditionalize the test instead of the output.
-
- Oct 28, 2017
-
-
Durham Goode authored
A recent refactor added a layer of abstraction to the dirstate which makes doing things like 'foo in dirstate' now require some extra Python attribute lookups. This is causing a 100ms slow down in hg status for mozilla-central. The fix is to hoist the inner dict's functions onto the main class once the lazy loading it complete, as well as store the actual functions before doing the status loop (as is done for other such functions). In my testing, it seems to address the performance regression, but we'll need to see the perf run results to know for sure. Differential Revision: https://phab.mercurial-scm.org/D1257
-
- Oct 26, 2017
-
-
Durham Goode authored
Before the recent refactor, we would not load the entire map until it was accessed. As part of the refactor, that got lost and even just trying to load the dirstate parents would load the whole map. This caused a perf regression (issue5713) and a regression with static http serving (issue5717). Making it lazy loaded again fixes both. Differential Revision: https://phab.mercurial-scm.org/D1253
-
Durham Goode authored
A future diff will move the lazy loading aspect of dirstate to the dirstatemap class. This means it requires a slightly different strategy of clearing than just reinstantiating the object (since just reinstantiating the object will lazily load the on disk data again later instead of remaining permanently empty). So let's give it it's own clear function. Differential Revision: https://phab.mercurial-scm.org/D1252
-
- Oct 27, 2017
-
-
Boris Feld authored
This explains the various usage and feature of the config register introduced in Mercurial 4.3 and 4.4.
-
Boris Feld authored
Gregory Szorc requested some clarification.
-
Boris Feld authored
The getbundle wireprotocol method has some extended documentation. We update it with the next parameters introduced for binary phases.
-
- Oct 28, 2017
-
-
Matt Harbison authored
The same applies to '?' if --quiet is used (or any of the other states if some of -marduic is specified), but I couldn't figure out how to express that clearly.
-
Matt Harbison authored
The paths being processed are from scmutil.status, and therefore normalized to '/' separators.
-
- Oct 26, 2017
-
-
Anton Shestakov authored
-
- Oct 25, 2017
-
-
Yuya Nishihara authored
This seems a bit hacky, but works well. There should be no reason that static-http repo had to load dirstate. Initially I tried to proxy os.stat() call through vfs so that statichttpvfs could hook it, but there wasn't a good error value which the statichttpvfs could return to get around the util.filestat issue.
-
Yuya Nishihara authored
This provides some confidence on files that should be loadable over HTTP. Hopefully it will prevent future bugs.
-
Yuya Nishihara authored
The logfile option was unused, so it was okay until now.
-
- Oct 24, 2017
-
-
Kevin Bullock authored
If we're going to use the user's installed and configured hg command (which we do since 8b20338b989e), we should prevent devel-warn messages from interfering with locating it.
-
Kevin Bullock authored
HGRCPATH is already set in localhgenv().
-
- Oct 20, 2017
-
-
Kevin Bullock authored
-
- Oct 23, 2017
-
-
muxator authored
"can only specify one of -C/--clean, -c/--check, or -m/merge" becomes "can only specify one of -C/--clean, -c/--check, or -m/--merge"
-
- Oct 04, 2017
-
-
muxator authored
The short options "-c" and "-C" may be confusing for a novice reading the documentation. Let's try to be more explicit, also mentioning the equivalent long options ("--check" and "--clean") in the comments.
-
- Oct 21, 2017
-
-
Yuya Nishihara authored
If the legacy pager extension is enabled, a pager is started through repo.ui at dispatch._runcommand(). After that, mqcommand() creates a qrepo with a fresh repo.baseui, at which point pager information was lost and another pager would be spawned by the modern pager interface. This is a minimal workaround for the problem.
-
Yuya Nishihara authored
This is the common pattern seen in the other registrar classes.
-
Yuya Nishihara authored
-
- Oct 20, 2017
-
-
Joe Blaylock authored
-
Kevin Bullock authored
-
Kevin Bullock authored
-
- Aug 05, 2017
-
-
Yuya Nishihara authored
This is alternative workaround to D1198, originally spotted by the earlier version of the releasenotes extension.
-
- Oct 20, 2017
-
-
Yuya Nishihara authored
-