Re: Commit fest queue - Mailing list pgsql-hackers

From Brendan Jurd
Subject Re: Commit fest queue
Date
Msg-id 37ed240d0804102107u27313c69k3904b3fb07ac8dec@mail.gmail.com
Whole thread Raw
In response to Re: Commit fest queue  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Apr 11, 2008 at 1:40 PM, Tom Lane  wrote:
> "Brendan Jurd"  writes:
>
> > Not really.  I'm claiming that, to the submitter, a response that
>  > hasn't happened yet and a response that is never coming look pretty
>  > much identical.
>
>  I understand, but that seems a bit offtopic seeing that this whole
>  thread is about how to guarantee that we don't actually forget about
>  any patches or bug reports.
>
>  If you want to make the responses faster, then you gotta pony up some
>  genuine human resources to deal with the problems.  Feel free to join
>  Bruce and me in the trenches.
>

I think we've gotten some wires crossed.  We are, in effect, arguing
the same point.  Upthread (and previously in other threads) I agreed
heartily with Heikki's comment that patch submitters should be putting
their work in the queue themselves.

I've been saying that I would happily add my own patches to the wiki.
That *is* contributing human resources to the problem.  And it is a
simple solution to my complaint above; that it can be a long time
before your patch moves into the queue.  Anyone who doesn't want to
wait for the Bruce Method to take effect can just do it for
themselves.

Cheers,
BJ


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: http://getfiregpg.org

iD8DBQFH/uPp5YBsbHkuyV0RAk/9AJsGjLVYpBx9J3zo6P1D8UsWqlS9FQCg1ZVw
py7s/5M+KJmkSvAH/osx9tA=
=77ab
-----END PGP SIGNATURE-----


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Commit fest queue
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Commit fest queue