Re: Concurrent psql patch

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, David Fetter <david(at)fetter(dot)org>, Jim Nasby <decibel(at)decibel(dot)org>, pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Concurrent psql patch
Date: 2008-04-09 02:26:37
Message-ID: 200804090226.m392QbO14282@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Andrew Dunstan wrote:
> > Are you suggesting we just delete the threads and let them die if they
> > don't submit a new version?
> >
> >
>
> My understanding was that all items in a commit-fest have one of these
> three dispositions:
>
> . committed
> . rejected
> . referred back to author for more work
>
> We're really only interested in the third one here, and so, yes, the
> ball should be in the author's court, not yours. I don't see any reason
> for you to move items from one queue to another like that. It just looks
> like it's making work.

True. I could move the emails back to my private mailbox and just track
them there too. I moved them so it would be visible we were waiting for
some people.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2008-04-09 02:29:26 Commit fest queue
Previous Message Bruce Momjian 2008-04-09 02:25:17 Re: Concurrent psql patch

Browse pgsql-patches by date

  From Date Subject
Next Message Shane Ambler 2008-04-09 02:36:40 Re: Concurrent psql API
Previous Message Bruce Momjian 2008-04-09 02:25:17 Re: Concurrent psql patch