From: Bruce Momjian <bruce@momjian.us>
Message-Id: <200805071421.m47ELmb00983@momjian.us>
Subject: Re: Posting to hackers and patches lists
In-Reply-To: <6229.1210169873@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wed, 7 May 2008 10:21:48 -0400 (EDT)
CC: PostgreSQL-development <pgsql-hackers@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > I think it would be helpful for us to provide an infrastructure where
> > people who don't run their own servers to store their patches at a
> > stable URL where they can keep updating the content.  I did that with
> > the psql wrap patch and it helped me.
> 
> Actually, I find that that is a truly awful habit and I wish that people
> would *not* do it that way.  There are two reasons why not:
> 
> * no permanent archive of the submitted patch
> 
> * reviewer won't know if the submitter changes the patch after he
> downloads a copy, and in fact nobody will ever know unless the submitter
> takes the time to compare the eventual commit to what he thinks the
> patch is

This requires the patch submitter to send an email every time they
update the URL.  The problem with no archive is a problem though.  It
works for me because I am around to supply versions but I see your
point --- perhaps we could make the system have a stable URL but allow
for versioning access.  Maybe email is a fine interface, of course.

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

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