To: "Josh Berkus" <josh@agliodbs.com>
Cc: <pgsql-hackers@postgresql.org>
Subject: Re: Posting to hackers and patches lists
In-Reply-To: <200805081043.54942.josh@agliodbs.com> (Josh Berkus's message of
	"Thu\, 8 May 2008 10\:43\:54 -0700")
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux)
References: <34d269d40805070752g4d578a1fu6acb00fd8e5f774e@mail.gmail.com>
	<34d269d40805070837q19f1144eu8c316fa1cf6d8780@mail.gmail.com>
	<4821D0A0.8040305@zeut.net> <200805081043.54942.josh@agliodbs.com>
From: Gregory Stark <stark@enterprisedb.com>
Organization: EnterpriseDB
Date: Thu, 08 May 2008 22:28:58 +0100
Message-ID: <87zlr0mqn9.fsf@oxford.xeocode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

"Josh Berkus" <josh@agliodbs.com> writes:

> How about hacking together a simple patch tracker instead, as Bruce suggested?  
> I've never found e-mail to be a particularly good way to track patches.  

The thing is that we don't just want to "track" patches. We want to talk about
patches.

In my ideal world we would mail off our patches to -hackers and the mail
software (this could be a subscription option) would strip them out before
forwarding the message. It would upload them to a web server and put a link in
the forwarded messages to the file on the web server.

If you have a clever IMAP server and a clever IMAP client you're actually not
far from that world today. But a lot of us are stuck with at least one
unclever piece of software there.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training!