From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Alex Shulgin <ash(at)commandprompt(dot)com> |
Cc: | Greg Smith <greg(at)2ndQuadrant(dot)com>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: automating CF submissions (was xlog location arithmetic) |
Date: | 2012-01-19 18:14:02 |
Message-ID: | 4F185D6A.1040302@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 01/19/2012 12:59 PM, Alex Shulgin wrote:
> Greg Smith<greg(at)2ndQuadrant(dot)com> writes:
>
>> One unicorn I would like to have here would give the CF app a database
>> of recent e-mails to pgsql-hackers. I login to the CF app, click on
>> "Add recent submission", and anything matching my e-mail address
>> appears with a checkbox next to it. Click on the patch submissions,
>> and then something like you described would happen. That would save
>> me the annoying work around looking up message IDs so much.
> Another idea: introduce some simple tag system in mails sent to -hackers
> to be treated specially, e.g:
>
> @fest add-to-current
>
> to add new patch to the commit fest currently in progress, or
>
> @fest add-to-next
>
> to add it to the next scheduled fest.
>
> Attribute your mail with
>
> @fest comment COMMENT TEXT
>
> or
>
> @fest comment<<EOF
> ...
> EOF
>
> to add a (long) comment, ditto for "patch" and "review".
>
> How does that sound?
>
Like a recipe for something that requires constant fixups, to be honest.
Seriously, adding something to the CF isn't *that* hard. I like Greg's
idea of a list of recent emails that you could choose from.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Shulgin | 2012-01-19 18:18:37 | Re: Postgres ReviewFest Patch: URI connection string support for libpq |
Previous Message | Robert Haas | 2012-01-19 18:10:39 | Re: Vacuum rate limit in KBps |