Re: pgsql: Remove references to Majordomo

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Remove references to Majordomo
Date: 2019-01-18 15:02:47
Message-ID: 24074.1547823767@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Fri, Jan 18, 2019 at 1:26 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>> Wouldn't it be better to also switch the references to pgsql-bugs in
>> all the C code for the different --help outputs?

> You are right, we definitely should. I'll go ahead and fix that. I can't
> quite make up my mind on if it's a good idea to backpatch that though --
> it's certainly safe enough to do, but it might cause issues for translators?

Yeah, weak -1 for back-patching. We don't usually like to thrash
translatable messages in the back branches.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2019-01-18 16:05:15 pgsql: Avoid sometimes printing both tables and their columns in DROP C
Previous Message Magnus Hagander 2019-01-18 10:38:51 Re: pgsql: Remove references to Majordomo

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Karlsson 2019-01-18 15:18:03 Re: Feature: temporary materialized views
Previous Message Stephen Frost 2019-01-18 14:50:40 Re: current_logfiles not following group access and instead follows log_file_mode permissions