From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.22-pre6-ac1
Date: 18 Jul 2003 14:02:43 +0100 [thread overview]
Message-ID: <1058533363.19512.39.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030718131714.A26615@infradead.org>
On Gwe, 2003-07-18 at 13:17, Christoph Hellwig wrote:
> On Fri, Jul 18, 2003 at 08:12:26AM -0400, Alan Cox wrote:
> > o The tty procfile can reveal keycounts make (Solar Designer)
> > it root only
>
> Shouldn't we just kill it completly?
It is useful in lots of situations, its just *too* useful in some of
them. I don't see a reason to kill it off
next prev parent reply other threads:[~2003-07-18 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 12:12 Linux 2.4.22-pre6-ac1 Alan Cox
2003-07-18 12:17 ` Christoph Hellwig
2003-07-18 13:02 ` Alan Cox [this message]
2003-07-25 9:01 ` Jerome Chantelauze
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=1058533363.19512.39.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=hch@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).