To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "Bruce Momjian" <bruce@momjian.us>,
	"Alvaro Herrera" <alvherre@commandprompt.com>,
	"Greg Smith" <gsmith@gregsmith.com>,
	"Pg Hackers" <pgsql-hackers@postgresql.org>
Subject: Re: Patch queue -> wiki
In-Reply-To: <27307.1207361987@sss.pgh.pa.us> (Tom Lane's message of "Fri\,
	04 Apr 2008 22\:19\:47 -0400")
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux)
References: <200804050114.m351E6900485@momjian.us>
	<87abk9dqah.fsf@oxford.xeocode.com> <27307.1207361987@sss.pgh.pa.us>
From: Gregory Stark <stark@enterprisedb.com>
Organization: EnterpriseDB
Date: Sat, 05 Apr 2008 03:37:08 +0100
Message-ID: <87wsndc9ij.fsf@oxford.xeocode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> Gregory Stark <stark@enterprisedb.com> writes:
>
>> The hard part is reading the email and figuring out
>> what status the patch is in.
>
> Certainly.  What we've got to do is make sure that after someone has
> made that decision, it doesn't cost them a couple of minutes of drudgery
> to look up the appropriate email-archives URL and push it into the wiki
> page (probably with a comment).  I can't imagine that this is terribly
> difficult, but web page scripting isn't one of my strengths ...

Hm, the way you describe this I fear we would get the list of every individual
email on the topic. What I think we want is usually to add a link to an
existing entry and update the status. That pretty much does require going to
the page and finding the entry in question.

It probably would be neat if the email footer thingy added a url to each email
it distributed via the lists pointing to the permanent message-id-based url in
the archives for that message. Then at least you would have that handy.


-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's 24x7 Postgres support!