mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Crispin Cowan <crispin@wirex.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What went wrong with LSM, was: Re: [BK PATCH] LSM changes for   2.5.59
Date: Thu, 13 Feb 2003 00:12:34 -0500	[thread overview]
Message-ID: <200302130512.h1D5CY909638@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1045110181.1643.linux-kernel2news@redhat.com>

>>>And here we see _the_ problem with the LSM process.  LSM wasn't
>>>developed as part of the broad kernel community (lkml) but on
>>>a rather small, almost private list.
>>>
>>Many of the things that you are saying in this discussion are untrue.
>>[...]
>>The bulk of the development process was carried out for more than two
>>years on the LSM development mailing list, which is fully public and open
>>to anyone.  It is not "almost private", whatever that is supposed to mean.

This is a situation, descibed by Douglas Adams in the opening
chapters of "Hitchiker's Guide to Galaxy". You put the vital info
somewhere, and when someone (who has to suffer if he does not see it)
fails to retrieve the info, it gets his own fault. It all was in
the open, so what else is to be desired?

I used to be super irritated by separate lists. Now I'm a member
of linux-usb-devel, uml-devel, sparclinux, and god knows what else.
Yes, they are unavoidable. Still, it is important to keep linux-kernel
at least somewhat informed. IMHO.

-- Pete

  parent reply	other threads:[~2003-02-13  5:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 16:58 Makan Pourzandi (LMC)
2003-02-12 18:45 ` 'Christoph Hellwig'
2003-02-12 19:11 ` magniett
2003-02-12 18:38   ` 'Christoph Hellwig'
2003-02-12 22:22     ` Crispin Cowan
2003-02-12 23:05       ` What went wrong with LSM, was: " 'Christoph Hellwig'
2003-02-12 23:24         ` Jesse Pollard
2003-02-13  1:02         ` James Morris
2003-02-13  4:19           ` Crispin Cowan
     [not found]           ` <mailman.1045110181.1643.linux-kernel2news@redhat.com>
2003-02-13  5:12             ` Pete Zaitcev [this message]
2003-02-13  6:52               ` Crispin Cowan
2003-02-13  1:56         ` Casey Schaufler
2003-02-13  4:37         ` Crispin Cowan

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=200302130512.h1D5CY909638@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=crispin@wirex.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome