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
Andrew Sullivan [EMAIL PROTECTED] 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
Tom Lane wrote:
Andrew Sullivan [EMAIL PROTECTED] 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
Andrew Dunstan wrote:
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
Stefan Kaltenbrunner wrote:
[ Discussion about making infrastructure downtime more visible to people.]
Right now, when email is down, I just start IM'ing people. A more
structured system would help me.
Some people would say a more structured approach to patch/bug tracking
would help
Bruce Momjian wrote:
This is an interesting observation that deserves to be discussed
separately, and relates to the patch queue. Many people want to know
what is happening with the patch queue but having better reporting
doesn't seem to help much the people who are actually processing the
Alvaro Herrera wrote:
Bruce Momjian wrote:
This is an interesting observation that deserves to be discussed
separately, and relates to the patch queue. Many people want to know
what is happening with the patch queue but having better reporting
doesn't seem to help much the people who
Bruce Momjian [EMAIL PROTECTED] writes:
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?
Uh, I don't think we have any patches for the next commit fest yet.
Bruce Momjian wrote:
Alvaro Herrera wrote:
I did manage to find actual patches, but I had then to resort to my own
mailbox to get the actual patch to apply and review.
You can download an mbox of the entire queue if that helps.
Ah, yeah, that's what I did.
Also I don't know what
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
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?
Uh, I don't think we have any patches for the
Alvaro Herrera wrote:
Bruce Momjian wrote:
Alvaro Herrera wrote:
I did manage to find actual patches, but I had then to resort to my own
mailbox to get the actual patch to apply and review.
You can download an mbox of the entire queue if that helps.
Ah, yeah, that's what I did.
Alvaro Herrera wrote:
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?
Yes. My experience is similar to yours. I'm not prepared to spend hours
Bruce Momjian [EMAIL PROTECTED] 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
Gregory Stark [EMAIL PROTECTED] 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
Gregory Stark wrote:
Bruce Momjian [EMAIL PROTECTED] 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,
Tom Lane wrote:
Gregory Stark [EMAIL PROTECTED] 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.
Bruce Momjian [EMAIL PROTECTED] 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
Gregory Stark wrote:
Bruce Momjian [EMAIL PROTECTED] 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
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
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
Bruce Momjian [EMAIL PROTECTED] 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/[EMAIL PROTECTED]
Huh, fascinating. it's actually an RSS feed.
I can fool
Gregory Stark wrote:
Bruce Momjian [EMAIL PROTECTED] 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/[EMAIL PROTECTED]
Huh, fascinating. it's
bruce wrote:
Gregory Stark wrote:
Bruce Momjian [EMAIL PROTECTED] 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/[EMAIL PROTECTED]
Huh,
23 matches
Mail list logo
