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.
Thu, 24 Sep 2015 00:50:06 -0700 mq: remove a mutable default argument
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.
Thu, 24 Sep 2015 00:49:02 -0700 largefiles: remove a mutable default argument
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.
Thu, 24 Sep 2015 00:48:24 -0700 largefiles: remove a mutable default argument
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.
Thu, 24 Sep 2015 00:48:02 -0700 largefiles: remove a mutable default argument
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.
Thu, 24 Sep 2015 00:46:37 -0700 largefiles: remove a mutable default argument
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.
Thu, 24 Sep 2015 00:46:12 -0700 largefiles: remove a mutable default argument
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.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 tip