On 3/29/17 4:56 PM, Jun Wu wrote:
Excerpts from Pierre-Yves David's message of 2017-03-29 13:24:39 +0200:
On 03/28/2017 08:59 PM, Ryan McElroy wrote:
On 3/27/17 2:11 PM, Augie Fackler wrote:
On Mon, Mar 27, 2017 at 09:18:55AM +0200, Pierre-Yves David wrote:
Sure, that seems like a good idea.
Excerpts from Pierre-Yves David's message of 2017-03-29 13:24:39 +0200:
>
> On 03/28/2017 08:59 PM, Ryan McElroy wrote:
> > On 3/27/17 2:11 PM, Augie Fackler wrote:
> >> On Mon, Mar 27, 2017 at 09:18:55AM +0200, Pierre-Yves David wrote:
> >>> Sure, that seems like a good idea. Can you see to it ?
On 03/28/2017 08:59 PM, Ryan McElroy wrote:
On 3/27/17 2:11 PM, Augie Fackler wrote:
On Mon, Mar 27, 2017 at 09:18:55AM +0200, Pierre-Yves David wrote:
Sure, that seems like a good idea. Can you see to it ?
It's a good idea, but I feel like the name "ProgrammingError" alone
provides some
On 3/27/17 2:11 PM, Augie Fackler wrote:
On Mon, Mar 27, 2017 at 09:18:55AM +0200, Pierre-Yves David wrote:
Sure, that seems like a good idea. Can you see to it ?
It's a good idea, but I feel like the name "ProgrammingError" alone
provides some clue as to what's going on, and the migration is
Sure, that seems like a good idea. Can you see to it ?
(I just replied on repair because this is the first changeset in the series)
On 03/27/2017 08:57 AM, Jun Wu wrote:
I think ProgrammingError should all have that hint. So this is not repair.py
specific.
Excerpts from Pierre-Yves David's
I think ProgrammingError should all have that hint. So this is not repair.py
specific.
Excerpts from Pierre-Yves David's message of 2017-03-27 08:27:51 +0200:
>
> On 03/27/2017 02:14 AM, Jun Wu wrote:
> > # HG changeset patch
> > # User Jun Wu
> > # Date 1490572408 25200
> > #
On 03/27/2017 02:14 AM, Jun Wu wrote:
# HG changeset patch
# User Jun Wu
# Date 1490572408 25200
# Sun Mar 26 16:53:28 2017 -0700
# Node ID 92d7eff3f4c7e44e8aab62b486bda78a37b73b83
# Parent e86eb75e74ce1b0803c26d86a229b9b711f6d76a
# Available At