Re: splitting debian-devel-changes

1998-01-19 Thread Santiago Vila
-BEGIN PGP SIGNED MESSAGE- On Fri, 16 Jan 1998, Martin Schulze wrote: > Are you completely uninterested how the ports are going on? No, I am not "completely uninteresed". But my interest is not so high to receive all those mails... Please, let's postpone this discussion until announceme

Re: splitting debian-devel-changes

1998-01-17 Thread Chris Lawrence
On Jan 16, Guy Maor wrote: > Chris Lawrence <[EMAIL PROTECTED]> writes: > > > Chris, who's spammed people with m68k uploads and is currently being > > spammed by sparc and alpha uploads. > > Surely you can program your mailer to throw away the mails about archs > that you're not interested in? I

Re: splitting debian-devel-changes

1998-01-17 Thread Guy Maor
Chris Lawrence <[EMAIL PROTECTED]> writes: > Chris, who's spammed people with m68k uploads and is currently being > spammed by sparc and alpha uploads. Surely you can program your mailer to throw away the mails about archs that you're not interested in? Guy

Re: splitting debian-devel-changes

1998-01-16 Thread Chris Lawrence
---Martin Schulze <[EMAIL PROTECTED]> wrote: > > On Fri, Jan 16, 1998 at 05:01:57PM +0100, Santiago Vila wrote: > > > > > Well, now that the Debian ports generate a lot of postings in > > > > debian-devel-changes, I think it is time to split that list by > > > > architecture. > > > >

Re: splitting debian-devel-changes

1998-01-16 Thread Martin Schulze
On Fri, Jan 16, 1998 at 05:01:57PM +0100, Santiago Vila wrote: > > > Well, now that the Debian ports generate a lot of postings in > > > debian-devel-changes, I think it is time to split that list by > > > architecture. > > > > Why not just use scoring in Gnus? > > We not just creat

Re: splitting debian-devel-changes

1998-01-16 Thread Santiago Vila
-BEGIN PGP SIGNED MESSAGE- On 14 Jan 1998, Karl M. Hegbloom wrote: > > "Santiago" == Santiago Vila <[EMAIL PROTECTED]> writes: > > > Well, now that the Debian ports generate a lot of postings in > > debian-devel-changes, I think it is time to split that list by > > archit

Re: splitting debian-devel-changes

1998-01-15 Thread Karl M. Hegbloom
> "Santiago" == Santiago Vila <[EMAIL PROTECTED]> writes: > Well, now that the Debian ports generate a lot of postings in > debian-devel-changes, I think it is time to split that list by > architecture. Why not just use scoring in Gnus?

Re: splitting debian-devel-changes

1998-01-09 Thread Christian Schwarz
em to have forgotten to CC to the list. Thanks for quoting me!) Just for completeness, here is my reply: Personally, I like the idea of splitting debian-devel-changes very much. Note, that we have already discussed a new uploading procedure where announcements will be sent by a script from mas

Re: splitting debian-devel-changes

1998-01-08 Thread Santiago Vila
-BEGIN PGP SIGNED MESSAGE- Well, as Christian Schwarz has pointed out to me (and I agree), it would be better to postpone this debate until the "new uploading procedure" is approved and installed (see the next "policy weekly posting"). Thanks. -BEGIN PGP SIGNATURE- Version: 2.6.3

Re: splitting debian-devel-changes

1998-01-08 Thread Martin Schulze
On Thu, Jan 08, 1998 at 06:43:55PM +1100, Martin Mitchell wrote: > I think a more complete approach is needed for this issue. Other things > which should be considered: > - Possibly a more compact format for upload announcements for binary-only > recompiles. What rushes to my mind is another t

Re: splitting debian-devel-changes

1998-01-08 Thread Martin Mitchell
Santiago Vila <[EMAIL PROTECTED]> writes: > Well, now that the Debian ports generate a lot of postings in > debian-devel-changes, I think it is time to split that list by > architecture. I think a more complete approach is needed for this issue. Other things which should be considered: - Changin

splitting debian-devel-changes

1998-01-07 Thread Santiago Vila
-BEGIN PGP SIGNED MESSAGE- Well, now that the Debian ports generate a lot of postings in debian-devel-changes, I think it is time to split that list by architecture. Two proposals: 1. "The easy one": Use debian-devel-changes for source packages, i386 packages, and binary-all packages, as