Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <4134AB9D.3010306@bristowhill.com>
References: <4134AB9D.3010306@bristowhill.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <FD5392AF-FBA0-11D8-81D2-003065905854@nonintuitive.com>
Content-Transfer-Encoding: 7bit
From: Samuel Andrew McIntyre <fuzzylogic@nonintuitive.com>
Subject: Re: Derby commit records are posted to derby-commits@db.apache.org
Date: Tue, 31 Aug 2004 15:56:27 -0700
To: "Derby Development" <derby-dev@db.apache.org>


On Aug 31, 2004, at 9:47 AM, Jean T. Anderson wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Originally I thought commit records were supposed to go to
> derby-dev@db.apache.org, but they are in fact going to
> derby-commits@db.apache.org
>
> So, any thoughts on this?
>
> ~ -jean

I personally would prefer the commit records on a separate list, for 
ease of browsing the commits and to keep the noise down  on derby-dev.

Plus, it looks like the Apache DB project suggests keeping separate 
commit lists on the project guidelines: 
http://db.apache.org/communication.html

While this doesn't appear to be strictly followed, maybe we can blaze a 
trail for standards compliance in this area. ;-)

Anyway, that's my $.02,

andrew