From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Brendan Jurd" <direvus(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, "PostgreSQL WWW" <pgsql-www(at)postgresql(dot)org>, "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec> |
Subject: | Re: [HACKERS] commitfest.postgresql.org |
Date: | 2009-07-03 20:00:06 |
Message-ID: | 727.1246651206@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> I think it IS newest at the bottom, and I agree that that is how it
>> should be.
> It seems to be inconsistent. Probably because everything wound up
> with the same date, the order is probably more-or-less random.
Yeah, I think that's what I'm seeing.
> What
> are the chances that the date or timestamp of the corresponding wiki
> modification could be put onto the patch and comment lines? (One
> would hope that could be done with a script, rather than by hand....)
Currently, it seems that most or all of the entries are links to
archived messages. Scraping the date from the underlying message
would be the best thing.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2009-07-03 20:09:13 | Re: [HACKERS] commitfest.postgresql.org |
Previous Message | Kevin Grittner | 2009-07-03 19:48:54 | Re: [HACKERS] commitfest.postgresql.org |
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2009-07-03 20:09:13 | Re: [HACKERS] commitfest.postgresql.org |
Previous Message | Kevin Grittner | 2009-07-03 19:48:54 | Re: [HACKERS] commitfest.postgresql.org |