public inbox for [email protected]  

help / color / mirror / Atom feed

From: Gregory Stark <[email protected]>
To: Tom Lane <[email protected]>
Cc: Matthew T. O'connor <[email protected]>
Cc: Alex Hunsaker <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Brendan Jurd <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Posting to hackers and patches lists
Date: Wed, 07 May 2008 21:08:42 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

"Tom Lane" <[email protected]> writes:

> "Matthew T. O'connor" <[email protected]> writes:
>> Patches are an integral part of the conversation about development, I 
>> think trying to split them up is awkward at best.  Do people really 
>> still think that the potential for larger messages is really a problem?  
>
> Personally I'd be fine with abandoning -patches and just using -hackers.
> We could try it for awhile, anyway, and go back if it seems worse.

I'm for that.

>> By the way, what is the actual size limit on hackers vs patches.
>
> They do have different size limits; we'd have to raise the limit on
> -hackers if we do this.  Marc would know exactly what the limits are.

Note that even the size limit on -patches is too small for some patches. 

What I did with previous large patches which were not getting through to
patches was put them up on a web page but with a new filename for each
version. So the URL for a given version *was* stable, the content never
changed. You could check the index page to see if there were more recent
versions.

I would suggest putting large patches up on the wiki in cases like that now,
but isn't there a size limit on the wiki too?

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

view thread (42+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Posting to hackers and patches lists
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox