Gregory Stark wrote:
>
>
> "Bruce Momjian" <bruce@momjian.us> writes:
>
> > Alvaro Herrera wrote:
> >>
> >> I'm not sure I follow. I tried last week to give some hours for patch
> >> review. What actually happened was that I had to wade through a ton of
> >> stuff, skipping patches that were already applied, threads that were
> >> purely discussion but not patches, threads about earlier versions of
> >> some patches.
> >
> > Yep, that describes the painful process well.
> >
> > I have tried to stay on top of patches already applied but I am doing a
> > clock sweep over the queue and you probably caught a spot I was nearing.
>
> I've also tried to find stuff I could review and failed repeatedly. I have a
> week now where I could spend a lot of time on this so I'll try again.
>
> Am i looking at the right list though? The one I'm looking at still starts
> with a patch to which Tom commented "This is superseded by a later submission"
> which I think has been there since pretty much the start of the commitfest.

Yes, those emails are kept for background material for the later patch.

> > You can download an mbox of the entire queue if that helps.
> >>
> >> Also I don't know what patches we have for the next commitfest. I would
> >> gladly give some time to put up a Wiki page to list the patches for the
> >> next commitfest. Would that be helpful?
>
> I tried this once already. I dumped the first page of Bruce's queue into a
> wiki page and laid it out in a column. But I wanted to add links back to the
> messages in the archive and ran into a problem with that. It also would have
> been a pain because Bruce's list is divided up into pages.

Yep, sorry.

> If we modify the archives to have a URL to go straight to a message-id and
> Bruce generated a list all on one page including comments and message-ids then
> I could process them all into a wiki page in a few hours.

Ideally we could have a message id link to the official archives. Off
list tell me what you want and I will generate it.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Tom Lane wrote:
> Gregory Stark <stark@enterprisedb.com> writes:
> > Am i looking at the right list though? The one I'm looking at still starts
> > with a patch to which Tom commented "This is superseded by a later submission"
> > which I think has been there since pretty much the start of the commitfest.
>
> Yeah, there is still a boatload of stuff that could be removed from the
> patch queue. I think that Bruce is intentionally leaving in all traffic
> related to an open patch, which is okay by me as long as the obsolete
> versions are properly commented. But I wish he'd get on with removing
> the stuff that is marked as already committed (some in 8.3!).

I am doing a clock sweep through the list, and it takes a week for each
cycle.

>
> > It also would have
> > been a pain because Bruce's list is divided up into pages.
>
> That's been a pain in the rear since the start. Bruce, could we combine
> it into one page now that it's relatively short?

Sure. Done.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

"Bruce Momjian" <bruce@momjian.us> writes:

>> I tried this once already. I dumped the first page of Bruce's queue into a
>> wiki page and laid it out in a column. But I wanted to add links back to the
>> messages in the archive and ran into a problem with that. It also would have
>> been a pain because Bruce's list is divided up into pages.
>
> Yep, sorry.
>
>> If we modify the archives to have a URL to go straight to a message-id and
>> Bruce generated a list all on one page including comments and message-ids then
>> I could process them all into a wiki page in a few hours.
>
> Ideally we could have a message id link to the official archives. Off
> list tell me what you want and I will generate it.

Well I was going to let this commit-fest go forward and then try to get what I
would want from you when a) the list is down to a manageable size and b) isn't
actively being used.

What I wanted was a page that included all comments, the message-id of each
message, the author of each message, and included everything on one page.


The other half of this was modifying the archives so that we had a URL we
could pass a message-id to. I think we all agreed that would be a wonderful
thing to have regardless of how we tackle this list anyways.

Magnus or Dave? Is there anything I can help with to get the URL to
message-ids going?

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

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Gregory Stark wrote:
> "Bruce Momjian" <bruce@momjian.us> writes:
>
> >> I tried this once already. I dumped the first page of Bruce's queue into a
> >> wiki page and laid it out in a column. But I wanted to add links back to the
> >> messages in the archive and ran into a problem with that. It also would have
> >> been a pain because Bruce's list is divided up into pages.
> >
> > Yep, sorry.
> >
> >> If we modify the archives to have a URL to go straight to a message-id and
> >> Bruce generated a list all on one page including comments and message-ids then
> >> I could process them all into a wiki page in a few hours.
> >
> > Ideally we could have a message id link to the official archives. Off
> > list tell me what you want and I will generate it.
>
> Well I was going to let this commit-fest go forward and then try to get what I
> would want from you when a) the list is down to a manageable size and b) isn't
> actively being used.
>
> What I wanted was a page that included all comments, the message-id of each
> message, the author of each message, and included everything on one page.

You can get the message-ids by grep'ing the mbox file, and the comments
are all:

http://js-kit.com/rss/momjian.us/msgid-*

e.g.

http://js-kit.com/rss/momjian.us/msg...stgresql.o rg

So, once you grep the message ids, you can just pull the comments using
the above URL with your current message-id. Is there anything else?

> The other half of this was modifying the archives so that we had a URL we
> could pass a message-id to. I think we all agreed that would be a wonderful
> thing to have regardless of how we tackle this list anyways.

Agreed.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Bruce Momjian wrote:

> > If we modify the archives to have a URL to go straight to a message-id and
> > Bruce generated a list all on one page including comments and message-ids then
> > I could process them all into a wiki page in a few hours.
>
> Ideally we could have a message id link to the official archives. Off
> list tell me what you want and I will generate it.

Hmm, there's the permalink stuff I mentioned via Jabber. I think you
could do this right away, and not wait until the next commitfest.

The other thing Greg is saying is to remove paginated output. You can
set mhonarc to put all messages in a single page. I'm not sure this is
such a hot idea for all users, because such a page would be humongous;
but perhaps runnning mhonarc twice is a good idea?

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > > If we modify the archives to have a URL to go straight to a message-id and
> > > Bruce generated a list all on one page including comments and message-ids then
> > > I could process them all into a wiki page in a few hours.
> >
> > Ideally we could have a message id link to the official archives. Off
> > list tell me what you want and I will generate it.
>
> Hmm, there's the permalink stuff I mentioned via Jabber. I think you
> could do this right away, and not wait until the next commitfest.
>
> The other thing Greg is saying is to remove paginated output. You can
> set mhonarc to put all messages in a single page. I'm not sure this is
> such a hot idea for all users, because such a page would be humongous;
> but perhaps runnning mhonarc twice is a good idea?

Done already --- we can always revert it.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

"Bruce Momjian" <bruce@momjian.us> writes:

> You can get the message-ids by grep'ing the mbox file, and the comments
> are all:
>
> http://js-kit.com/rss/momjian.us/msgid-*
>
> e.g.
>
> http://js-kit.com/rss/momjian.us/msg...stgresql.o rg

Huh, fascinating. it's actually an RSS feed.

I can fool around with this. I should be able to snarf in the mbox and format
a wiki page with the comments from js-kit and links to the message-id.

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

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Gregory Stark wrote:
> "Bruce Momjian" <bruce@momjian.us> writes:
>
> > You can get the message-ids by grep'ing the mbox file, and the comments
> > are all:
> >
> > http://js-kit.com/rss/momjian.us/msgid-*
> >
> > e.g.
> >
> > http://js-kit.com/rss/momjian.us/msg...stgresql.o rg
>
> Huh, fascinating. it's actually an RSS feed.
>
> I can fool around with this. I should be able to snarf in the mbox and format
> a wiki page with the comments from js-kit and links to the message-id.

Alvaro reminded me that '@' can be used in a URL, just not in the host
name part, so I have converted over to using messsge-ids for permanent
URLs, e.g.:

http://momjian.us/mhonarc/patches/44...isedb.com.html

I will keep the MD5 URLs too as well until this commit fest is over.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On Mon, Mar 24, 2008 at 06:39:25PM -0400, Andrew Dunstan wrote:

> perusing a mailbox again. We have unfortunately been badly underprepared
> for this.

Surely that there is an emerging consensus to that effect means that it's
not as unfortunate as it might be? I seem to recall the original
announcement suggesting this was an experiment. I wouldn't expect the first
couple rounds to go without a hitch; as long as there is procedural
improvement the next time, that's a good thing, right?

A


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Andrew Sullivan <ajs@crankycanuck.ca> writes:
> On Mon, Mar 24, 2008 at 06:39:25PM -0400, Andrew Dunstan wrote:
>> perusing a mailbox again. We have unfortunately been badly underprepared
>> for this.

> Surely that there is an emerging consensus to that effect means that it's
> not as unfortunate as it might be? I seem to recall the original
> announcement suggesting this was an experiment. I wouldn't expect the first
> couple rounds to go without a hitch; as long as there is procedural
> improvement the next time, that's a good thing, right?

Yeah, we expected to have glitches. I think we now have a much better
idea what sort of status-tracking support we need for future fests.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers