Re: A typo in a messsage?

2023-12-31 Thread Kyotaro Horiguchi 
At Wed, 27 Dec 2023 13:34:50 +0700, John Naylor  wrote 
in 
> > Shouldn't the "is" following "LSN" be "in"?
> 
> Pushed.

At Wed, 27 Dec 2023 13:35:24 +0700, John Naylor  wrote 
in 
>> I think "crc" should be in all uppercase in general and a brief
>> grep'ing told me that it is almost always or consistently used in
>> uppercase in our tree.
> I pushed this also.

Thanks for pushing them!

regads.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

Re: A typo in a messsage?

2023-12-26 Thread John Naylor 
On Fri, Dec 22, 2023 at 1:50 PM Kyotaro Horiguchi
 wrote:
>
> I found the following message introduced by a recent commit.
>
> > errdetail("The first unsummarized LSN is this range is %X/%X.",
>
> Shouldn't the "is" following "LSN" be "in"?

Pushed.

Re: A typo in a messsage?

2023-12-22 Thread John Naylor 
On Fri, Dec 22, 2023 at 1:50 PM Kyotaro Horiguchi
 wrote:
>
> I found the following message introduced by a recent commit.
>
> > errdetail("The first unsummarized LSN is this range is %X/%X.",
>
> Shouldn't the "is" following "LSN" be "in"?

I think you're right, will push.