Re: getting rid of maintainer-check

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: getting rid of maintainer-check
Date: 2013-09-04 15:09:03
Message-ID: CA+Tgmob-K_9BAB9_=n7gYxbpT69hAELWfk27Ych-DfXT5WX-5A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 3, 2013 at 10:41 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> The maintainer-check target never really caught on, I think. Most
> people don't run it, and that in turn annoys those who do. Also, it
> doesn't provide much functionality.
>
> I propose that we get rid of it and roll the functionality into the
> regular build.
>
> Specifically:
>
> - Running duplicate_oids during the regular build was already discussed
> elsewhere recently. There are some details to be resolved there, but
> it's doable.
>
> - Checking for tabs in SGML files can be run during the regular
> documentation build without problems.
>
> - The NLS checks can also be run during the regular NLS-enabled build.
>
> That's it. Any concerns?

I can't speak for anyone else, but personally I think that sounds like
a significant improvement.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kohei KaiGai 2013-09-04 15:10:29 Re: [v9.4] row level security
Previous Message Andres Freund 2013-09-04 15:04:47 Re: 9.4 regression