public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrew Dunstan <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: We have no Windows critters contributing typedef lists
Date: Wed, 7 Mar 2018 11:10:32 +1030
Message-ID: <CAA8=A78xhP4yo-Tcg0MUTpwVsQcm1Yqayfc-cSL+9Ng+WdT13w@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

On Wed, Mar 7, 2018 at 8:55 AM, Tom Lane <[email protected]> wrote:
> A pgindent run I just did showed me that we no longer have entries in
> the buildfarm's typedefs list for any typedefs that are used only in
> EXEC_BACKEND builds --- and, I suppose, none for Windows-only code
> either.  I suppose that one of the recently deceased Windows animals
> was the only one contributing those.  We need to improve this situation
> before it's time to run pgindent again.
>
> I'm not sure what the infrastructure requirements are for extracting
> typedefs from Windows builds.
>


Nothing special I think. I have just enabled it for jacana and also
for bowerbird which I am reviving. Basically it's just a matter of
adding
    find_typedefs => {},
to the optional_steps part of the config file. That will make it get
the typedefs for every build of every branch.

You should see some results in a few hours.

cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

view thread (4+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: We have no Windows critters contributing typedef lists
  In-Reply-To: <CAA8=A78xhP4yo-Tcg0MUTpwVsQcm1Yqayfc-cSL+9Ng+WdT13w@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox