Re: Improving prep_buildtree used in VPATH builds - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Improving prep_buildtree used in VPATH builds
Date
Msg-id AANLkTinv_bSVXvpvNrbP-EgMY48unQ=BsX9viXrf9sqb@mail.gmail.com
Whole thread Raw
In response to Re: Improving prep_buildtree used in VPATH builds  (Gurjeet Singh <singh.gurjeet@gmail.com>)
Responses Re: Improving prep_buildtree used in VPATH builds
List pgsql-hackers
On Mon, Sep 27, 2010 at 10:18 AM, Gurjeet Singh <singh.gurjeet@gmail.com> wrote:
> On Mon, Sep 27, 2010 at 4:15 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
>>
>>
>> On 09/27/2010 10:11 AM, Robert Haas wrote:
>>>
>>>> What should be the value of 'Message-ID for original patch' ?
>>>> the URL:
>>>> http://archives.postgresql.org/pgsql-hackers/2010-09/msg01837.php
>>>> or the ID: AANLkTinw0HL+jQmrtwXC9Y2tqhcfHFgFekxyyfYGvQrB@mail.gmail.com
>>>
>>> The latter.
>>>
>>
>> Could this perhaps be made clearer on the page, perhaps with an example?
>> It confused me recently too.
>>
>
> Or maybe populate the drop-down with every available topic from previous
> CFs, and add an additional '(Add new topic)' to the drop-down which would
> take you to topic creation page.

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>.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Heads up: upcoming back-branch releases
Next
From: Tom Lane
Date:
Subject: Re: Large objects.