Skip site navigation (1) Skip section navigation (2)

Re: Improving prep_buildtree used in VPATH builds

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improving prep_buildtree used in VPATH builds
Date: 2010-09-27 14:54:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Andrew's question seemed to be about the message-ID.  I agree the
> topic thing is confusing, though.  I'm wondering if it would be
> sufficient to do the following - if no topic are available, instead of
> showing the form, it says something like:

> No topics have been created for this CommitFest yet.  Before adding
> your patch, you must add one or more items to the <link>topic
> list</link>.

I liked the idea of pre-populating with the historical set of topics.
If you encourage the first few submitters to a new CF to invent their
own topic categories without any guidance, you're going to get some
crazy topics.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2010-09-27 14:59:45
Subject: Re: gist access methods parameter types
Previous:From: Tom LaneDate: 2010-09-27 14:50:34
Subject: Re: Large objects.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group