Joerg Sonnenberger <joerg@bec.de> [Fri, 26 Jan 2018 17:31:50 +0100] rev 35852
mdiff: remove rewindhunk by yielding a bool first to indicate data
Differential Revision: https://phab.mercurial-scm.org/D1942
Joerg Sonnenberger <joerg@bec.de> [Fri, 26 Jan 2018 02:14:39 +0100] rev 35851
mdiff: explicitly compute places for the newline marker
Differential Revision: https://phab.mercurial-scm.org/D1941
Joerg Sonnenberger <joerg@bec.de> [Thu, 25 Jan 2018 22:40:19 +0100] rev 35850
patch: avoid repeated binary checks if all files in a patch are text
Differential Revision: https://phab.mercurial-scm.org/D1940
Martin von Zweigbergk <martinvonz@google.com> [Thu, 01 Feb 2018 10:29:24 -0800] rev 35849
setdiscovery: don't call "heads" wire command when heads specified
Our custom server has too many heads to announce (one per code review,
plus a public head), but it still lets the user request one of them by
doing
hg pull -r <some expression>
After the client has resolved the expression to a set of nodeids by
calling the "lookup" wire command, it will start the discovery
phase. Before this patch, that doesn't take the requested heads into
account and unconditionally calls the server's "heads" command to find
all its heads. One consequence of that the "all remote heads known
locally" case triggers if the client already had the public head and
the user will see a "no changes found" message that's unrelated to the
head they requested. That message confused me for a while. More
imporantly, it also means that pullop.cgresult incorrectly (given our
arguably misbehaving server) gets set to 0 (no changesets added),
which confused some of our extensions.
This patch makes it so the client skips the "heads" command if the
user requested specific revisions.
Since the "heads" command is normally batched with the first "known"
command and calculating the list of heads is probably cheap, I don't
expect much improvement in speed from this.
Differential Revision: https://phab.mercurial-scm.org/D1962
Martin von Zweigbergk <martinvonz@google.com> [Thu, 01 Feb 2018 08:17:11 -0800] rev 35848
testrunner: on error, color the "(case xxx)" part the same as filename
When using #testcases, the lines that read something like
ERROR: test-split.t (case obsstore-off) output changed
get colored red and the filename gets highlighted with a brighter
red. This makes it harder to notice the "case obsstore-off" part, but
it does seem important, so let's highlight it.
Differential Revision: https://phab.mercurial-scm.org/D1959
Augie Fackler <augie@google.com> [Thu, 18 Jan 2018 10:08:23 -0500] rev 35847
python3: whitelist an additional 23 passing tests
Differential Revision: https://phab.mercurial-scm.org/D1908
Augie Fackler <augie@google.com> [Thu, 18 Jan 2018 09:58:40 -0500] rev 35846
tests: fix a missed b prefix in a test extension in test-strip.t
# skip-blame just a bytes prefix
Differential Revision: https://phab.mercurial-scm.org/D1907
Augie Fackler <augie@google.com> [Thu, 18 Jan 2018 09:14:30 -0500] rev 35845
revlog: correct type in check to verify rawtext is immutable
This fixes far more failures than I feel like it has any right to, so
there's clearly some subtle interaction between self._cache and other
parts of this code. :(
Differential Revision: https://phab.mercurial-scm.org/D1906
Augie Fackler <augie@google.com> [Wed, 17 Jan 2018 22:05:37 -0500] rev 35844
mq: use bytes() instead of str() to encode statusentries for writing
Differential Revision: https://phab.mercurial-scm.org/D1903
Augie Fackler <augie@google.com> [Wed, 17 Jan 2018 22:05:02 -0500] rev 35843
mq: open status file et al in bytes mode
Differential Revision: https://phab.mercurial-scm.org/D1902