From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Help text for pg_basebackup -R |
Date: | 2017-02-18 12:49:50 |
Message-ID: | CABUevEwqzNsd7HW2STC8UYNp5GNTT41962ZkyWB5+yonG=jsRQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 17, 2017 at 5:21 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > * Alvaro Herrera (alvherre(at)2ndquadrant(dot)com) wrote:
> >> Magnus Hagander wrote:
> >>> I'm guessing if we backpatch something like that, it would cause
> issues for
> >>> translations, right? So we should make it head only?
>
> >> We've had the argument a number of times. My stand is that many
> >> translators are active in the older branches, so this update would be
> >> caught there too; and even if not, an updated English message is better
> >> than an outdated native-language message.
>
> > That makes sense to me, at least, so +1, for my part.
>
> Yeah, if the existing message text is actually wrong or misleading,
> we should back-patch. I'm not sure I would do that if it's just a
> cosmetic improvement. In this particular case, +1.
>
OK. Applied and backpatched.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2017-02-18 13:13:02 | Re: Gather Merge |
Previous Message | Fabien COELHO | 2017-02-18 12:44:53 | Re: [HACKERS] Small issue in online devel documentation build |