Re: Bison 3.0 updates

From: Greg Stark <stark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Marti Raudsepp <marti(at)juffo(dot)org>, PGBuildFarm <pgbuildfarm-members(at)pgfoundry(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bison 3.0 updates
Date: 2013-07-29 19:04:02
Message-ID: CAM-w4HMYKbsLKf1wE3WZFjcAoXGEH8En8Ss6sLzjbM1RAY0azw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members pgsql-hackers

On Mon, Jul 29, 2013 at 4:05 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I can see both sides of this. It's definitely nice to get early warning
> when toolchain changes create new problems for Postgres, but it's not
> clear that the buildfarm is the best way to get such notifications.

Perhaps something as simple as choosing a sufficiently oddball or
frightening animal name?

predator or alien?
killerbee? bedbug?

--
greg

In response to

Browse buildfarm-members by date

  From Date Subject
Next Message Jeff Janes 2013-07-29 19:19:00 Re: Bison 3.0 updates
Previous Message Andrew Dunstan 2013-07-29 18:45:22 Re: Bison 3.0 updates

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2013-07-29 19:19:00 Re: Bison 3.0 updates
Previous Message Andrew Dunstan 2013-07-29 18:45:22 Re: Bison 3.0 updates