Thu, 24 Sep 2015 10:37:13 -0700 lock: add a method to prepare the lock for inheritance
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.
Thu, 24 Sep 2015 15:57:11 -0700 lock: introduce state to keep track of inheritance
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.
Thu, 24 Sep 2015 10:53:16 -0700 error: add an exception to indicate lock inheritance API contract violations
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
Thu, 24 Sep 2015 15:52:11 -0700 clone: check update rev for being True
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).
Thu, 24 Sep 2015 15:47:23 -0700 clone: fix over-indented continuation line
Sean Farley <sean@farley.io> [Thu, 24 Sep 2015 15:47:23 -0700] rev 26353
clone: fix over-indented continuation line
Fri, 25 Sep 2015 03:51:46 -0400 resolve: consistently describe re-merge + unresolved
timeless@mozdev.org [Fri, 25 Sep 2015 03:51:46 -0400] rev 26352
resolve: consistently describe re-merge + unresolved
Thu, 10 Sep 2015 16:53:07 +0200 mercurial: add debugextensions command (issue4676)
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.
Thu, 24 Sep 2015 10:15:37 +0300 dispatch: stop warning about EPIPE in --debug mode
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.
Mon, 14 Sep 2015 17:31:48 -0700 rebase: don't rebase obsolete commit whose successor is already rebased
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"
Thu, 24 Sep 2015 00:34:15 -0700 check-code: forbid mutable value for default argument
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.
Thu, 24 Sep 2015 00:54:30 -0700 httpconnection: remove a mutable default argument
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.
Thu, 24 Sep 2015 00:52:21 -0700 transplant: remove a mutable default argument
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.
(0) -10000 -3000 -1000 -300 -100 -12 +12 +100 +300 +1000 +3000 +10000 tip