I'm happy to know such a thing. mcxt.c is very stable part of the
code so those who don't know such things like me rarely comes.
At Thu, 23 Feb 2017 22:59:51 -0500, Tom Lane wrote in
<31880.1487908...@sss.pgh.pa.us>
> Andres Freund writes:
> > On 2017-02-23 14:26:07 -0600, Jim Nasby wrote:
> >>
Andres Freund writes:
> On 2017-02-23 14:26:07 -0600, Jim Nasby wrote:
>> On 2/23/17 6:38 AM, Thomas Munro wrote:
>>> That is an archaic way of contracting the same words differently:
>> Given the number of non-native English speakers we have, it's probably worth
>> changing it...
> I'm a non-na
On 2017-02-23 14:26:07 -0600, Jim Nasby wrote:
> On 2/23/17 6:38 AM, Thomas Munro wrote:
> > > I'm not so confident, but the "'tis" seems to me to be a typo of
> > > "it's".
> > That is an archaic way of contracting the same words differently:
>
> Given the number of non-native English speakers we
On 2/23/17 6:38 AM, Thomas Munro wrote:
I'm not so confident, but the "'tis" seems to me to be a typo of
"it's".
That is an archaic way of contracting the same words differently:
Given the number of non-native English speakers we have, it's probably
worth changing it...
--
Jim Nasby, Data Ar
On Thu, Feb 23, 2017 at 5:40 PM, Kyotaro HORIGUCHI
wrote:
> Hello, while I investigated a bug of async-exec patch. I found a
> (maybe) typo in mcxt.c.
>
> | * It's not entirely clear whether 'tis better to do this before or after
> | * delinking the context; but an error in a callback will likel
Hello, while I investigated a bug of async-exec patch. I found a
(maybe) typo in mcxt.c.
| * It's not entirely clear whether 'tis better to do this before or after
| * delinking the context; but an error in a callback will likely result in
I'm not so confident, but the "'tis" seems to me to be