From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, 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-04 03:14:02 |
Message-ID: | 603c8f070907032014u11c5f274r826c2f824ab5cd23@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
On Fri, Jul 3, 2009 at 4:00 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "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.
I think what you guys must be seeing is that the topics are not in
quite the same order. As far as I can tell, the ordering of patches
within topics is absolutely identical. If you see a counterexample,
please point it out. If you want to fix the order of the topics,
click on the "CommitFest Topics" link in the upper lefthand corner of
the page and frobnicate the sort order.
>> 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.
Brendan, is this something that you can work on? Or does anyone else
have some time to put into it? And do we have to fix this before we
can declare the new system live, or can we catch up after the fact?
Because replicating changes from the old system to the new is a bit of
a pain in the neck.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Jurd | 2009-07-04 03:42:37 | Re: [HACKERS] commitfest.postgresql.org |
Previous Message | Robert Haas | 2009-07-04 03:11:02 | Re: commitfest.postgresql.org |
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Jurd | 2009-07-04 03:42:37 | Re: [HACKERS] commitfest.postgresql.org |
Previous Message | Robert Haas | 2009-07-04 03:11:02 | Re: commitfest.postgresql.org |