Mon, 21 Apr 2014 15:48:52 -0700 bundle2: gracefully handle abort during unbundle stable
Pierre-Yves David <pierre-yves.david@fb.com> [Mon, 21 Apr 2014 15:48:52 -0700] rev 21177
bundle2: gracefully handle abort during unbundle Clients expect a bundle2 reply to their bundle2 submission. So we catch the Abort error and turn it into a bundle2 containing a part transporting the exception data. The unbundling of this reply will raise the error again.
Tue, 22 Apr 2014 11:22:41 -0700 bundle2: decorate exception raised during bundle processing stable
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 22 Apr 2014 11:22:41 -0700] rev 21176
bundle2: decorate exception raised during bundle processing This is a small hack to help us do some graceful error handling in bundle2 without major refactoring. See embedded comment for details.
Tue, 22 Apr 2014 10:14:16 -0300 histedit, i18n: replace '+' with concatenation to make hggettext happy stable
Wagner Bruna <wbruna@softwareexpress.com.br> [Tue, 22 Apr 2014 10:14:16 -0300] rev 21175
histedit, i18n: replace '+' with concatenation to make hggettext happy
Tue, 22 Apr 2014 10:12:21 -0300 commands: fix typo in --graph description stable
Wagner Bruna <wbruna@softwareexpress.com.br> [Tue, 22 Apr 2014 10:12:21 -0300] rev 21174
commands: fix typo in --graph description
Tue, 22 Apr 2014 10:12:13 -0300 revset, i18n: add translator comment to "only" stable
Wagner Bruna <wbruna@softwareexpress.com.br> [Tue, 22 Apr 2014 10:12:13 -0300] rev 21173
revset, i18n: add translator comment to "only"
Mon, 21 Apr 2014 20:24:54 +0200 merge: improve notes for listing the bids for ambiguous merges stable
Mads Kiilerich <madski@unity3d.com> [Mon, 21 Apr 2014 20:24:54 +0200] rev 21172
merge: improve notes for listing the bids for ambiguous merges
Fri, 18 Apr 2014 13:33:20 +0200 merge: tell the user when we are using bid merge stable
Mads Kiilerich <madski@unity3d.com> [Fri, 18 Apr 2014 13:33:20 +0200] rev 21171
merge: tell the user when we are using bid merge Bid merge is a new rarely used feature that the user explicitly enabled - we should tell/warn when the user actually is using it, just like we tell when we not are using it. Give a message like note: merging 3b08d01b0ab5+ and adfe50279922 using bids from ancestors 0f6b37dbe527 and 40663881a6dd
Mon, 21 Apr 2014 20:22:14 +0200 merge: fix stray character in bid merge message stable
Mads Kiilerich <madski@unity3d.com> [Mon, 21 Apr 2014 20:22:14 +0200] rev 21170
merge: fix stray character in bid merge message
Mon, 21 Apr 2014 20:18:42 +0200 tests: better test coverage for bid merge stable
Mads Kiilerich <madski@unity3d.com> [Mon, 21 Apr 2014 20:18:42 +0200] rev 21169
tests: better test coverage for bid merge Martin Geisler's test case revealed the previous message argument error.
Mon, 21 Apr 2014 19:53:19 +0200 merge: fix wrong number of arguments for bid merge message stable
Mads Kiilerich <madski@unity3d.com> [Mon, 21 Apr 2014 19:53:19 +0200] rev 21168
merge: fix wrong number of arguments for bid merge message
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip