From: Bruce Momjian <bruce@momjian.us>
Message-Id: <200805071503.m47F3xi10638@momjian.us>
Subject: Re: Posting to hackers and patches lists
In-Reply-To: <34d269d40805070752g4d578a1fu6acb00fd8e5f774e@mail.gmail.com>
To: Alex Hunsaker <badalex@gmail.com>
Date: Wed, 7 May 2008 11:03:59 -0400 (EDT)
CC: Brendan Jurd <direvus@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Alex Hunsaker wrote:
> >  Right, I was assuming once the patch was uploaded it would be to our
> >  infrastructure and would be permanent.
> 
> Heck, I dont think patch submitters really care.  And Ill do whatever
> is in the dev faq.
> But Its a heck of a lot easier (for me) just to send them in email.

Sure, then just keep sending them via email.  I often go through several
revisions a day as I get feedback and having all that email volume seems
wasteful.

> Plus it seems awkward to move a discussion thats taking place on
> -hackers over to patches... Granted I could post to patches first,
> wait an hour then send an email to hackers/reviewer and say hey!
> updated patch here!  But it hardly seems worth it to me...  In fact I
> would argue -patches should go away so we dont have that split.

The goal is for the patches list to just discuss patches, but often
there are user API issues that come up after the patch is submitted, and
people often want that discussion on hackers.  The current email split
can certainly be awkward.

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

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