Re: Use of term hostaddrs for multiple hostaddr values
От | Magnus Hagander |
---|---|
Тема | Re: Use of term hostaddrs for multiple hostaddr values |
Дата | |
Msg-id | CABUevExxHqFEsxnzEJ+UuvBcUi=prU0dhKH0xwrEYD25rQPS7w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Use of term hostaddrs for multiple hostaddr values (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
Ответы |
Re: Use of term hostaddrs for multiple hostaddr values
|
Список | pgsql-hackers |
On Sun, Jan 21, 2018 at 12:45 AM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
On 1/20/18 17:39, Michael Paquier wrote:
> On Sat, Jan 20, 2018 at 08:30:43PM +0200, Magnus Hagander wrote:
>> On Tue, Jan 9, 2018 at 5:34 AM, Michael Paquier <michael.paquier@gmail.com>
>> wrote:
>> These are both clear bugs, and the docs one should definitely be both
>> applied and backpatched.
>>
>> How much do we care about the error message when it comes to backpatching?
>> Maybe we should leave that one to 11 only, to avoid breaking that, as the
>> way it's written it's actually less wrong there.
>>
>> Thoughts?
>
> Thanks for your input!
>
> Applying the error message portion only on HEAD is a good plan, there is
> no point to make the life of translaters unnecessary painful.
I would backpatch both. The updated error message is arguably easier to
translate.
Fair enough. And since you do the translation merging at least, I'll go with that.
Thus, applied and backpatched to 10.
Thanks!
В списке pgsql-hackers по дате отправления: