[EMAIL PROTECTED] (Joey Hess) wrote:
>Ben Collins wrote:
>> The lists already exist, they are just not used at all. Maybe it would be
>> easier to keep just the one debian-devel-changes list to send to and write
>> some extra procmail stuff into sending it to the write outlist.
>
>Well, we could ju
Ben Collins <[EMAIL PROTECTED]> writes:
> On Fri, Mar 17, 2000 at 04:49:54PM -0500, Bob Hilliard wrote:
> > During the slink freeze there was some discussion of the wasted
> > bandwidth due to -devel-announce and -announce listing all packages
> > installed/uploaded to all architectures.
> >
Ben Collins wrote:
> > As I recall, the consensus was that, after slink was released,
> > these lists would be split by architecture, and anyone interested in
> > more than one architecture could subscribe to as many lists as
> > required. I am sure that the overwhelming majority would subscr
On Fri, Mar 17, 2000 at 04:49:54PM -0500, Bob Hilliard wrote:
> During the slink freeze there was some discussion of the wasted
> bandwidth due to -devel-announce and -announce listing all packages
> installed/uploaded to all architectures.
>
> As I recall, the consensus was that, afte
Previously Zed Pobre wrote:
> It's a fairly common ruleset, I think. You can have mine.
That can be done a lot simpler:
:0:
* ^X-Mailing-List:.*debian-devel-changes
{
:0
* ^Subject:.*\((alpha|arm|powerpc|m68k|sparc)\)
/dev/null
:0
debian-devel-changes/
}
Tom Lees <[EMAIL PROTECTED]> wrote:
> On Sat, Mar 18, 2000 at 05:30:41PM +0100, Paul Seelig wrote:
> > Currently i've subscribed to devel-changes on another mail account which
> > only serves for sorting out the relevant (at least for me) parts. These
> > are sorted out using procmail (which is no
In article <[EMAIL PROTECTED]> you wrote:
> It might be he wants to talk about -changes ? There he's right (and I do
> totally agree with him).
I'm not excited about a list per architecture, but I've often wondered if
only posting to the lists messages for uploads that include source might not
be
Branden Robinson <[EMAIL PROTECTED]> writes:
>
>
> --n8g4imXOkfNTN/H1
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Fri, Mar 17, 2000 at 04:49:54PM -0500, Bob Hilliard wrote:
> > During the slink freeze there
Tom Lees <[EMAIL PROTECTED]> writes:
> On Sat, Mar 18, 2000 at 05:30:41PM +0100, Paul Seelig wrote:
> > Currently i've subscribed to devel-changes on another mail account which
> > only serves for sorting out the relevant (at least for me) parts. These
> > are sorted out using procmail (which is
On Sat, Mar 18, 2000 at 05:30:41PM +0100, Paul Seelig wrote:
> Currently i've subscribed to devel-changes on another mail account which
> only serves for sorting out the relevant (at least for me) parts. These
> are sorted out using procmail (which is not supported by my usual mail
> server) and a
On Sat, 18 Mar 2000, Branden Robinson wrote:
> On Fri, Mar 17, 2000 at 04:49:54PM -0500, Bob Hilliard wrote:
> > During the slink freeze there was some discussion of the wasted
> > bandwidth due to -devel-announce and -announce listing all packages
> > installed/uploaded to all architectures.
On Fri, Mar 17, 2000 at 04:49:54PM -0500, Bob Hilliard wrote:
> During the slink freeze there was some discussion of the wasted
> bandwidth due to -devel-announce and -announce listing all packages
> installed/uploaded to all architectures.
Funny, I don't notice any such messages going to -
On Fri, 17 Mar 2000, Bob Hilliard wrote:
> As I recall, the consensus was that, after slink was released,
> these lists would be split by architecture, and anyone interested in
> more than one architecture could subscribe to as many lists as
> required. I am sure that the overwhelming majori
13 matches
Mail list logo
