From: Josh Berkus <josh@agliodbs.com>
Organization: PostgreSQL @ Sun
To: pgsql-hackers@postgresql.org
Subject: Re: Posting to hackers and patches lists
Date: Thu, 8 May 2008 10:43:54 -0700
User-Agent: KMail/1.8.2
References: <34d269d40805070752g4d578a1fu6acb00fd8e5f774e@mail.gmail.com>
	<34d269d40805070837q19f1144eu8c316fa1cf6d8780@mail.gmail.com>
	<4821D0A0.8040305@zeut.net>
In-Reply-To: <4821D0A0.8040305@zeut.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200805081043.54942.josh@agliodbs.com>

Matt,

> Patches are an integral part of the conversation about development, I
> think trying to split them up is awkward at best. =A0Do people really
> still think that the potential for larger messages is really a problem? =
=A0

Well, I for one would need to change my subscription address.  This e-mailb=
ox=20
has a limit of 60MB.  I have 5 e-mail accounts, though, so I could figure=20
something out.  In this day and age of Google/Yahoo/MSN unlimited accounts,=
=20
list volume isn't quite the problem it once was.

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

=2D-=20
Josh Berkus
PostgreSQL @ Sun
San Francisco