All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marco d'Itri" <md@Linux.IT>
To: Andrew Gierth <andrew@erlenstar.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bincancels in linux.kernel
Date: Thu, 5 Dec 2002 01:44:07 +0100	[thread overview]
Message-ID: <20021205004407.GA7367@wonderland.linux.it> (raw)
In-Reply-To: <87fztd9u8j.fsf@erlenstar.demon.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]

On Dec 05, Andrew Gierth <andrew@erlenstar.demon.co.uk> wrote:

 > Marco> I'm not sure if there is a consensus about binaries in linux.*
 > Marco> groups which do not match *.binar*. OTOH last year I added
 > Marco> linux.* to the default cleanfeed configuration linux.* in the
 > Marco> list of groups where binaries are permitted and nobody ever
 > Marco> complained.
 >did they notice, though?
Who knows? But I suppose they will notice if this would ever become a
problem.

 >(I'd suggest linux.binaries.*, if not for the fact that people would
 >probably start posting distribution CDs and apps there.)
Everything should be gated below linux.binaries.* then...
The reason I think it's acceptable to not do this is that the traffic is
low even when a few binaries are gated.
Someday[1] I plan to create a linux.binaries.patches group to distribute
kernel patches, but as usual it will be moderated.

 > Marco> If you want to be sure that the hierarchy is not hijacked by
 > Marco> warez kiddies you can just cancel everything not posted from
 > Marco> /\.bofh\.it$/.
 >you could have put that in cleanfeed too :-)
At the time I still hoped to be able to switch the groups to moderated
soon.


[1] Or closer, if somebody will contribute a script able to detect new
kernel patches in a kernel.org mirror...
-- 
ciao,
Marco

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-12-05  0:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02 22:18 bincancels in linux.kernel Erik Hensema
2002-12-02 22:30 ` Jeff Garzik
2002-12-02 22:39   ` Larry McVoy
2002-12-03  0:09   ` H. Peter Anvin
2002-12-03  1:49 ` Andrew Gierth
2002-12-03  3:49   ` Rene Herman
2002-12-03 13:12   ` Marco d'Itri
2002-12-05  0:37     ` Andrew Gierth
2002-12-05  0:44       ` Marco d'Itri [this message]
2002-12-04  2:21   ` David Schwartz
2002-12-04  4:52     ` Andrew Gierth
2002-12-04  5:10       ` David Schwartz
     [not found] <fa.fv5l6nv.1am209b@ifi.uio.no>
     [not found] ` <fa.jsbpciv.t2snp4@ifi.uio.no>
2002-12-03  4:10   ` Russ Allbery
2002-12-03 13:19     ` bill davidsen
     [not found] ` <fa.eas3r1v.k3isq5@ifi.uio.no>
2002-12-03  8:25   ` Giacomo Catenazzi
2002-12-03 10:18     ` Miquel van Smoorenburg
     [not found] <fa.d6sj37v.97gj3h@ifi.uio.no>
     [not found] ` <fa.frmc8vv.pkcm2i@ifi.uio.no>
2002-12-04  3:50   ` Russ Allbery
  -- strict thread matches above, loose matches on Subject: below --
2002-12-05  1:02 Adam J. Richter

Reply instructions:

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

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

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021205004407.GA7367@wonderland.linux.it \
    --to=md@linux.it \
    --cc=andrew@erlenstar.demon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.