Yuya Nishihara <yuya@tcha.org> [Sat, 26 Sep 2015 11:25:38 +0900] rev 26369
help: define list of keywords that should be excluded from non-verbose output
This list will be reused by the other deprecated/experimental handling.
Matt Mackall <mpm@selenic.com> [Fri, 25 Sep 2015 23:10:47 -0500] rev 26368
merge with stable
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 25 Sep 2015 13:30:49 -0700] rev 26367
unbundle: cleanly abort on unknown bundle2 feature
The exception wasn't caught and resulted in a traceback.
Jordi Gutiérrez Hermoso <jordigh@octave.org> [Mon, 14 Sep 2015 19:25:34 -0400] rev 26366
phases: return zero for no-op operations (
issue4751) (BC)
It is rather unhelpful to return 1 if there were no changes because
the request matches the current state of phases. So we just undo that.
timeless@mozdev.org [Thu, 24 Sep 2015 14:45:17 -0400] rev 26365
help: add config.troubleshooting section at the top
Jordi Gutiérrez Hermoso <jordigh@octave.org> [Fri, 25 Sep 2015 11:16:20 -0400] rev 26364
dispatch: don't stack trace on commands like `hg .log`
This used to stack trace because it raised a util.Abort which wasn't
handled in this block. We now handle it. Additionally, we error out
earlier instead of plodding on and showing the "log" entry of the
plain `hg help` output.
Anton Shestakov <av6@dwimlabs.net> [Fri, 25 Sep 2015 12:38:20 +0800] rev 26363
gitweb, monoblue: port highlighting linked lines from paper
This is adapted from
41c4bdd1d585,
fbfe5748ef3e and
f3393d458bf5.
Anton Shestakov <av6@dwimlabs.net> [Fri, 25 Sep 2015 03:02:38 +0800] rev 26362
gitweb, monoblue: fix vertical align of spans in .sourcelines
Empty lines in file view could produce an inexplicable margin before the next
line (most noticeable in browsers on webkit/blink engine). That was making
empty lines seem taller than the rest.
Instead of using default vertical align, let's set it to 'top'.
This issue is actually present in paper, and only recently got into gitweb
(
2239626369f5) and monoblue (
119202d4d7a4). There's a bit more to it in paper,
so that will be dealt with in a future patch.
Recipe to see live: preferably using a webkit/blink browser, such as chromium,
browse a file with empty lines, e.g. https://selenic.com/hg/file/3.5/README#l8
Selecting a block of text that includes empty lines will reveal white "breaks"
in the selection. Highlighted line (#l8) also shows such a break below itself.
timeless@mozdev.org [Fri, 25 Sep 2015 00:54:20 -0400] rev 26361
merge: fix mergestate comment
timeless@mozdev.org [Thu, 24 Sep 2015 17:51:05 -0400] rev 26360
rebase: avoid losing branch commits with --keepbranch (
issue4835)
Siddharth Agarwal <sid0@fb.com> [Thu, 24 Sep 2015 16:03:26 -0700] rev 26359
lock.release: do not unlink inherited locks
This is part of a series that will allow locks to be inherited by subprocesses
in limited circumstances. A subprocess unlinking a lock will lead to potential
corruption from other concurrent processes.
Siddharth Agarwal <sid0@fb.com> [Thu, 24 Sep 2015 16:00:41 -0700] rev 26358
lock: add a method to reacquire the lock after subprocesses exit
This is part of a series that will allow locks to be inherited by subprocesses
in limited circumstances.
Siddharth Agarwal <sid0@fb.com> [Thu, 24 Sep 2015 10:37:13 -0700] rev 26357
lock: add a method to prepare the lock for inheritance
This is part of a series that will allow locks to be inherited by subprocesses
in limited circumstances.
Siddharth Agarwal <sid0@fb.com> [Thu, 24 Sep 2015 15:57:11 -0700] rev 26356
lock: introduce state to keep track of inheritance
This is part of a series that will allow locks to be inherited by subprocesses
in limited circumstances. In upcoming patches we will refer to this state.
Siddharth Agarwal <sid0@fb.com> [Thu, 24 Sep 2015 10:53:16 -0700] rev 26355
error: add an exception to indicate lock inheritance API contract violations
Sean Farley <sean@farley.io> [Thu, 24 Sep 2015 15:52:11 -0700] rev 26354
clone: check update rev for being True
In
30be3aeb5344, there was an attempt to fallback to looking up the update
revision assuming it was always a rev but the documentation states:
True means update to default rev, anything else is treated as a revision
Therefore, we should only fallback to looking up the update rev if it is not
True. This bug was found in hg-git and I couldn't think of a test that does
this in pure Mercurial since the source repository is checked for the revision
as well (and therefore gracefully falls back).
Sean Farley <sean@farley.io> [Thu, 24 Sep 2015 15:47:23 -0700] rev 26353
clone: fix over-indented continuation line
timeless@mozdev.org [Fri, 25 Sep 2015 03:51:46 -0400] rev 26352
resolve: consistently describe re-merge + unresolved
liscju <piotr.listkiewicz@gmail.com> [Thu, 10 Sep 2015 16:53:07 +0200] rev 26351
mercurial: add debugextensions command (
issue4676)
Add debugextensions command to help users debug their extension
problems. If there are no extensions command prints nothing,
otherwise it prints names of extension modules. If quiet or
verbose option is not specified it prints(after extensions name)
last version of mercurial in which given module was tested for
non internal modules or not tested with user mercurial version.
If verbose is specified it prints following information for every
extension: extension name, import source, testedwith and buglink
information.
Extensions are printed sorted by extension name.
Daniel Colascione <dancol@fb.com> [Thu, 24 Sep 2015 10:15:37 +0300] rev 26350
dispatch: stop warning about EPIPE in --debug mode
It seems silly for "hg --debug manifest | less" to print a scary
message after the user hits "q" in less. hg should just exit silently
instead, since EPIPE on stdout is a perfectly reasonable result.
Laurent Charignon <lcharignon@fb.com> [Mon, 14 Sep 2015 17:31:48 -0700] rev 26349
rebase: don't rebase obsolete commit whose successor is already rebased
This patch avoids unnecessary conflicts to resolve during rebase for the users
of changeset evolution.
This patch modifies rebase to skip obsolete commits if they are being rebased on
their successors.
It introduces a new rebase state 'revprecursor' for these revisions that are
being skipped and a new message to inform the user of what is happening.
This feature is gated behind the config flag experimental.rebaseskipobsolete
When an obsolete commit is skipped, the output is:
not rebasing 14:
9ad579b4a5de "I", already in destination as 17:
fc37a630c901 "K"
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:34:15 -0700] rev 26348
check-code: forbid mutable value for default argument
default value are common to all call. Using mutable value is a classical source
of bug in Python. We forbid it.
The regexp (Courtesy of Matt Mackall) is only catching such value on the first
line of a definition, but that will be good enough for now.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:54:30 -0700] rev 26347
httpconnection: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:52:21 -0700] rev 26346
transplant: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:50:06 -0700] rev 26345
mq: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs. The
underlying function already handle "None" as an option value, so we do not need
to do anything else.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:49:02 -0700] rev 26344
largefiles: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:48:24 -0700] rev 26343
largefiles: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:48:02 -0700] rev 26342
largefiles: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:46:37 -0700] rev 26341
largefiles: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:46:12 -0700] rev 26340
largefiles: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:44:59 -0700] rev 26339
largefiles: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:44:32 -0700] rev 26338
largefiles: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:41:43 -0700] rev 26337
largefiles: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:40:53 -0700] rev 26336
largefiles: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:38:34 -0700] rev 26335
histedit: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 01:07:09 -0700] rev 26334
templater: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 01:06:41 -0700] rev 26333
templater: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 01:06:10 -0700] rev 26332
templater: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 01:05:21 -0700] rev 26331
templater: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 01:04:58 -0700] rev 26330
templater: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 01:04:10 -0700] rev 26329
addremove: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 01:00:43 -0700] rev 26328
match: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs. We
added support for None in the underlying function in the parent commit.
therefore we do not need to do anything but passing None.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 01:00:25 -0700] rev 26327
match: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 01:00:05 -0700] rev 26326
match: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:59:26 -0700] rev 26325
match: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 01:58:33 -0700] rev 26324
addremove: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:56:30 -0700] rev 26323
tag: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs. We
just added support of None for the underlying function, so nothing else the
required.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 24 Sep 2015 00:56:18 -0700] rev 26322
commit: remove a mutable default argument
Mutable default arguments are know to the state of California to cause bugs.
Siddharth Agarwal <sid0@fb.com> [Tue, 22 Sep 2015 14:09:42 -0700] rev 26321
lock: move acquirefn call to inside the lock
We're going to need to call it again as part of reinitialization after a
subprocess inherits the lock.
Siddharth Agarwal <sid0@fb.com> [Tue, 22 Sep 2015 13:25:41 -0700] rev 26320
localrepo: call lock.lock with releasefn as a keyword arg
We'll be adding an acquirefn argument soon, and this makes that clearer.
Matt Mackall <mpm@selenic.com> [Wed, 19 Aug 2015 15:11:17 -0500] rev 26319
copies: move debug statement to appropriate place
Matt Mackall <mpm@selenic.com> [Wed, 19 Aug 2015 14:05:42 -0500] rev 26318
bidmerge: choose shortest list of diverge and rename/delete warnings
Slightly less arbitrary than choosing the first set.
Matt Mackall <mpm@selenic.com> [Wed, 19 Aug 2015 14:04:54 -0500] rev 26317
copies: rename diverge2 to divergeset for clarity
Matt Mackall <mpm@selenic.com> [Wed, 19 Aug 2015 13:40:18 -0500] rev 26316
copies: begin separating mergecopies sides
Matt Mackall <mpm@selenic.com> [Wed, 19 Aug 2015 13:09:54 -0500] rev 26315
copies: rename ctx() to getfctx() for clarity
Anton Shestakov <av6@dwimlabs.net> [Wed, 23 Sep 2015 16:02:35 +0800] rev 26314
monoblue: port code selection without line numbers from gitweb
This is adapted from
2239626369f5.
It also fixes
issue4790 in monoblue; tab characters now have meaningful width on
the modified pages (file view, file diff, changeset).
Kevin Bullock <kbullock@ringworld.org> [Tue, 22 Sep 2015 15:10:24 -0500] rev 26313
help: copy-edit description of ui.supportcontact
Siddharth Agarwal <sid0@fb.com> [Tue, 22 Sep 2015 16:56:34 -0700] rev 26312
ui: avoid mutable default arguments
I almost introduced a bug around this code by accidentally mutating a default
argument. There's no reason for these to exist.
It is OK to not assign {} to environ in ui.system because util.system knows how
to deal with that.
Siddharth Agarwal <sid0@fb.com> [Tue, 22 Sep 2015 16:55:18 -0700] rev 26311
util: avoid mutable default arguments
I almost introduced a bug around this code by accidentally mutating a default
argument. There's no reason for these to exist.
Yuya Nishihara <yuya@tcha.org> [Sun, 13 Sep 2015 18:01:01 +0900] rev 26310
obsstore: fast path to check if obsstore is empty
Yuya Nishihara <yuya@tcha.org> [Sun, 13 Sep 2015 17:52:37 +0900] rev 26309
obsstore: delay loading markers from obsstore file
This will allow us to use cached revisions without parsing obsstore.
Because _version isn't determined at __init__, the debugobsconvert command no
longer works correctly. I'll fix it by a separate patch for the evolve
extension.
Yuya Nishihara <yuya@tcha.org> [Sun, 13 Sep 2015 17:47:18 +0900] rev 26308
obsstore: initialize _all markers without using _addmarkers()
The next patch will make _all variable propertycached to avoid costly parsing
of obsstore. This means we can't call _addmarkers() to initialize _all.
Because all cached markers depend on _all, it isn't necessary to update these
caches when _all is initially loaded.
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 23 Sep 2015 00:41:07 -0700] rev 26307
revset: avoid implicit None testing in revset
Implicit None testing is a very good way to get in trouble. We explicitly test
for None.
Durham Goode <durham@fb.com> [Sun, 20 Sep 2015 16:53:42 -0700] rev 26306
revset: speed up existence checks for ordered filtered sets
Previously, calling 'if foo:' on a ordered filtered set would start iterating in
whatever the current direction was and return if a value was available. If the
current direction was ascending, but the set had a fastdesc available, this
meant we did a lot more work than necessary.
If this was applied without my previous max/min fixes, it would improve max()
performance (this was my first attempt at fixing the issue). Since those
previous fixes went in though, this doesn't have a visible benefit in the
benchmarks, but it does seem clearly better than it was before so I think it
should still go in.
Durham Goode <durham@fb.com> [Sun, 20 Sep 2015 19:27:53 -0700] rev 26305
revset: remove existence check from min() and max()
min() and max() would first do an existence check. Unfortunately existence
checks can be slow in certain situations (like if the smartset is a list, and
quickly iterable in both ascending and descending directions, then doing an
existence check will start from the bottom, even if you want to check the
max()).
The fix is to not do the check, and just handle the error if it happens. In a
large repo, this speeds up:
hg log -r 'max(parents(. + .^) - (. + .^) & ::master)'
from 3.5s to 0.85s. That revset is contrived and just for testing. In our
real case we used 'bundle()' in place of '. + .^'
Interesting perf numbers for the revset benchmarks:
max(draft() and ::tip) => 0.027s to 0.0005s
max(author(lmoscovicz)) => 2.48s to 0.57s
min doesn't show any perf changes, but changing it as well will prevent a perf
regression in my next patch.
Result from revset benchmark
revset #0: draft() and ::tip
min max
0) 0.001971 0.001991
1) 0.001965 0.000428 21%
revset #1: ::tip and draft()
min max
0) 0.002017 0.001912
1) 0.001896 94% 0.000421 22%
revset #2: author(lmoscovicz)
min max
0) 1.049033 1.358913
1) 1.042508 0.319824 23%
revset #3: author(lmoscovicz) or author(mpm)
min max
0) 1.042512 1.367432
1) 1.019750 0.327750 23%
revset #4: author(mpm) or author(lmoscovicz)
min max
0) 1.050135 0.324924
1) 1.070698 0.319913
revset #5: roots((tip~100::) - (tip~100::tip))
min max
0) 0.000671 0.001018
1) 0.000605 90% 0.000946 92%
revset #6: roots((0::) - (0::tip))
min max
0) 0.149714 0.152369
1) 0.098677 65% 0.100374 65%
revset #7: (20000::) - (20000)
min max
0) 0.051019 0.042747
1) 0.035586 69% 0.016267 38%
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 18 Sep 2015 17:23:10 -0700] rev 26304
update: move default destination into a revset
This is another step toward having "default" destination more clear and unified.
Not all the logic is there because some bookmark related computation happened
elsewhere. It will be moved later.
The function is private because as for the other ones, cleanup is needed before
we can proceed.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 17 Sep 2015 14:03:15 -0700] rev 26303
merge: move default destination computation in a revset
This is another step toward having "default" destination more clear and unified.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 17 Sep 2015 12:44:52 -0700] rev 26302
mergecmd: simplify conditional
The previous if tested the same thing with 'if repo._activebookmark'. We make the
if/else logic clearer before a bigger refactoring.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 17 Sep 2015 10:59:52 -0700] rev 26301
rebase: move destination computation in a revset
This is the first step toward making the "default destination" logic more clear
and unified. The revset is private because I'm happy to delay the bikeshedding until
after the clean up happened.
Augie Fackler <augie@google.com> [Tue, 22 Sep 2015 14:47:18 -0400] rev 26300
debian: include bash completions in mercurial-common
Augie Fackler <augie@google.com> [Tue, 22 Sep 2015 14:32:17 -0400] rev 26299
debian: install hgk as part of mercurial-common (
issue4829)
Leaving the hgk binary in /usr/bin causes some lintian warnings, and
downstream packages poke it in /usr/share/mercurial, so we'll just
stash it in there. Rather than patch hgk.py as part of the Mercurial
install, just drop a config file in /etc/mercurial/hgrc.d that points
to the installed hgk.
Augie Fackler <augie@google.com> [Tue, 22 Sep 2015 14:14:05 -0400] rev 26298
debian: install config files as part of mercurial-common
Future patches will start putting config files in /etc/mercurial/,
this just installs them.
Augie Fackler <augie@google.com> [Tue, 22 Sep 2015 14:31:17 -0400] rev 26297
debian: configuration so that cacerts is properly loaded
This will be included in the mercurial-common package in a followup
patch.
Augie Fackler <augie@google.com> [Tue, 22 Sep 2015 14:13:07 -0400] rev 26296
debian: install hg-ssh to /usr/bin just like downstream
Yuya Nishihara <yuya@tcha.org> [Sun, 20 Sep 2015 20:13:27 +0900] rev 26295
highlight: remove temporary hack to overwrite repo.getcwd
Now hgweb does it globally.
Yuya Nishihara <yuya@tcha.org> [Sun, 20 Sep 2015 20:11:31 +0900] rev 26294
hgweb: overwrite cwd to resolve file patterns relative to repo (
issue4568)
It's useless to handle file patterns as relative to the cwd of the server
process. The only sensible way in hgweb is to resolve paths relative to the
repository root.
It seems dirstate.getcwd() isn't used to get a real file path, so this patch
won't cause problem.
Yuya Nishihara <yuya@tcha.org> [Sun, 20 Sep 2015 20:08:22 +0900] rev 26293
dirstate: state that getcwd() shouldn't be used to get real file path
hgweb will force it to be '' so that file patterns can be resolved relative
to the repository root. I want to clarify that is correct.
Siddharth Agarwal <sid0@fb.com> [Wed, 16 Sep 2015 12:36:21 -0700] rev 26292
merge: move merge step to the end
Resolving other conflicts before merge ones is better because the state before
the merge is as consistent as possible. It will also help with future work
involving automatic resolution of merge conflicts with an external merge
driver.
There are no ordering issues here because it is easy to verify that the same
file is never in both the dg/dm and the m sets.
Siddharth Agarwal <sid0@fb.com> [Wed, 16 Sep 2015 19:52:06 -0700] rev 26291
lock: factor out lock testing into a separate function
This is going to be needed for upcoming work with lock inheritance.
Siddharth Agarwal <sid0@fb.com> [Wed, 16 Sep 2015 19:26:59 -0700] rev 26290
lock: factor code to read lock into a separate function
This is going to be needed for upcoming work with lock inheritance.
Siddharth Agarwal <sid0@fb.com> [Thu, 17 Sep 2015 15:38:00 -0700] rev 26289
tests: add unit tests for locking code
We're going to make significant changes to lock behavior soon.
Anton Shestakov <av6@dwimlabs.net> [Tue, 22 Sep 2015 02:09:10 +0800] rev 26288
gitweb: port code selection without line numbers from paper
This is adapted from
f2e4fdb3dd27 and
e92d4b8530cb.
It also fixes
issue4790 in gitweb; tab characters now have meaningful width on
the modified pages (file view, file diff, changeset).
Yuya Nishihara <yuya@tcha.org> [Sun, 13 Sep 2015 22:34:58 +0900] rev 26287
obsolete: remove unused _knownrevs function
The call site was removed at
cd62532c62a1.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 17 Sep 2015 16:08:10 -0700] rev 26286
bookmark: do not crash when active bookmark is forward and --date is used
The logic that decides where to update according to the active bookmark
location (when not on ".") was setting the rev to update to before we process
--date. This lead to --date processing aborting because of duplicated
specification.
We reorder the two pieces of code and add a test for this.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 17 Sep 2015 17:17:54 -0700] rev 26285
bookmark: actually test update behavior in both cases
The test claimed to test pull --update behaved the same way as pull + update,
but the behavior of pull + update was never tested.
We now test both.
Anton Shestakov <av6@dwimlabs.net> [Fri, 18 Sep 2015 14:03:32 +0800] rev 26284
coal: reuse style-paper.css and use a separate css file for visual tweaks
To remove another big chunk of duplication from coal hgweb style, we can move
all visual tweaks to style-extra-coal.css and include it together with
style-paper.css.
Anton Shestakov <av6@dwimlabs.net> [Fri, 18 Sep 2015 01:06:27 +0800] rev 26283
coal: reuse all templates from paper/map by %including the file
Before, coal/map simply had all the templates copied and pasted from paper/map
file. It was easy to make a change to paper that would get into coal only
partially and just sit there until something like
399e970e35c8 happened.
Let's remove this duplication from coal/map by using %include to reuse
templates from paper/map directly.
timeless@mozdev.org [Fri, 04 Sep 2015 05:40:52 -0400] rev 26282
help/config: reword committemplate external editor text
timeless@mozdev.org [Fri, 04 Sep 2015 05:40:37 -0400] rev 26281
help/config: reword committemplate multibyte character text
timeless@mozdev.org [Fri, 28 Aug 2015 15:43:14 -0400] rev 26280
help/config: use :hg:`help config....` notation
timeless@mozdev.org [Fri, 28 Aug 2015 15:24:58 -0400] rev 26279
help/config: omit True or False
timeless@mozdev.org [Fri, 28 Aug 2015 15:13:28 -0400] rev 26278
help/config: capitalize items
timeless@mozdev.org [Thu, 17 Sep 2015 21:20:35 -0400] rev 26277
tests: add more doctests for check-translation deprecated
timeless@mozdev.org [Thu, 17 Sep 2015 21:20:17 -0400] rev 26276
tests: cleanup check-translation deprecated
Anton Shestakov <av6@dwimlabs.net> [Fri, 18 Sep 2015 14:24:53 +0800] rev 26275
gitweb: add author to filelogentry
The line is copied from shortlogentry template.
Anton Shestakov <av6@dwimlabs.net> [Fri, 18 Sep 2015 14:24:38 +0800] rev 26274
monoblue: add author to filelogentry
The line is copied from shortlogentry template.
Anton Shestakov <av6@dwimlabs.net> [Fri, 18 Sep 2015 14:23:44 +0800] rev 26273
monoblue: split a long line in filelogentry template
The whole td has a nowrap class, which disallows breaking the line, so it's not
required to use non-breakable spaces.
Yuya Nishihara <yuya@tcha.org> [Fri, 18 Sep 2015 21:32:43 +0900] rev 26272
readbundle: fix typo of None compression
The test simulates pre-
d1b16a746db6 hgweb that sends "unbundle" capability
with no argument.
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 11 Sep 2015 17:06:56 -0700] rev 26271
readbundle: map 'HG10UN' to None compression
In line with the other previous changes
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 11 Sep 2015 17:06:02 -0700] rev 26270
getsubset: use None to request uncompressed changegroup
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 11 Sep 2015 17:05:46 -0700] rev 26269
bundle: use None when unpacking uncompressed changegroup
Let's be more modern!
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 15 Sep 2015 17:43:54 -0700] rev 26268
writebundle: use 'None' instead of 'UN' for the bundle2 case
Let's be modern!
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 15 Sep 2015 17:53:28 -0700] rev 26267
compression: use 'None' for no-compression
This seems more idiomatic and clearer. We still support both None and 'UN' for
now because no user are migrated.
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 15 Sep 2015 17:35:32 -0700] rev 26266
changegroup: move all compressions utilities in util
We'll reuse the compression for other things (next target bundle2), so let's
make it more accessible and organised.
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 15 Sep 2015 13:12:03 -0700] rev 26265
obsolete: clarify that 'successorssets' returns the latest successors
We do not return the first successors we found, we returns the latest (non
obsolete (mostly)) one following the obsolete link transitively. We update the
documentation to make this clean.
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 15 Sep 2015 13:10:25 -0700] rev 26264
obsolete: drop an empty line at the end of a docstring
This empty line is useless, let's drop it.
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 11 Sep 2015 12:45:19 -0700] rev 26263
traceback: allow providing a local support contact point
The extensions blaming code is fine for casual users but pretty terrible for
corporate environments that can deploy a large amount of extensions to
unsuspecting users. Reports will likely blame a random "innocent" extension (in
our case crecord) and the hint in the message will triggers endless debug
attempts from the user.
We introduce a "ui.supportcontact" option that allow such big company to redirect
their users to their own support desk. This disables all extensions blaming and
just point people to the local support in all cases.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 17 Sep 2015 11:50:55 -0700] rev 26262
dispatch: pre-indent the extensions blaming logic
We are about to put some real conditional here, but pre-indenting in it's own
changesets makes next patch much cleaner.
timeless@mozdev.org [Thu, 17 Sep 2015 07:49:18 -0400] rev 26261
tests: check for inconsistently translated DEPRECATED
Mercurial expects DEPRECATED to be translated consistently,
not doing that breaks Mercurial.
timeless@mozdev.org [Thu, 17 Sep 2015 07:33:21 -0400] rev 26260
i18n-fr: reject translation which is missing DEPRECATED
timeless@mozdev.org [Thu, 17 Sep 2015 07:47:30 -0400] rev 26259
i18n-pt_BR: select a single definition of DEPRECATED
Mercurial expects DEPRECATED to be translated consistently,
not doing that breaks Mercurial.
timeless@mozdev.org [Thu, 17 Sep 2015 07:37:20 -0400] rev 26258
i18n-sv: select a single definition of DEPRECATED
Mercurial expects DEPRECATED to be translated consistently,
not doing that breaks Mercurial.
timeless@mozdev.org [Thu, 17 Sep 2015 07:34:27 -0400] rev 26257
i18n-ro: use ()s instead of [] for DEPRECATED
timeless@mozdev.org [Thu, 17 Sep 2015 07:34:13 -0400] rev 26256
i18n-ro: include translation of DEPRECATED
timeless@mozdev.org [Thu, 17 Sep 2015 07:35:03 -0400] rev 26255
i18n-zh_CN: include translation of DEPRECATED
timeless@mozdev.org [Thu, 17 Sep 2015 07:33:44 -0400] rev 26254
i18n-it: include translation of DEPRECATED
timeless@mozdev.org [Thu, 17 Sep 2015 07:32:28 -0400] rev 26253
i18n-da: include translation of DEPRECATED
timeless@mozdev.org [Thu, 17 Sep 2015 07:31:07 -0400] rev 26252
test-i18n: always run non gettext tests
Yuya Nishihara <yuya@tcha.org> [Tue, 15 Sep 2015 00:32:39 +0900] rev 26251
localrepo: refresh filecache stats only if transaction finished successfully
If commit is aborted by pretxncommit hook, in-memory changelog and manifest
have entries that would be added. So they must be discarded on invalidate().
But the mechanism introduced by
a710936c3037 doesn't handle this case well.
It tries to mitigate the penalty of invalidate() by marking in-memory cache
as "clean" on unlock assuming that they are identical to the stored data.
But this assumption is wrong if stored data are rolled back by tr.abort().
This patch moves the hook to post-close action so that it will never be
triggered on abort.
This bug was originally reported to thg, which is only reproducible in
command-server process on unix, evolve disabled.
https://bitbucket.org/tortoisehg/thg/issues/4285/
Yuya Nishihara <yuya@tcha.org> [Tue, 15 Sep 2015 21:00:28 +0900] rev 26250
localrepo: move closure of lock release to class
It only captures "self", so it isn't necessary to be created dynamically.