From: Rene Rebe <rene.rebe@gmx.net>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: viro@math.psu.edu, greg@kroah.com, jonathan@daria.co.uk,
linux-kernel@vger.kernel.org
Subject: Re: Q: device(file) permissions for USB
Date: Fri, 7 Dec 2001 01:35:46 +0100 [thread overview]
Message-ID: <20011207013546.586f8948.rene.rebe@gmx.net> (raw)
In-Reply-To: <200112070021.fB70Lik02148@vindaloo.ras.ucalgary.ca>
In-Reply-To: <20011207005707.6a09706a.rene.rebe@gmx.net> <Pine.GSO.4.21.0112061903230.29985-100000@binet.math.psu.edu> <200112070021.fB70Lik02148@vindaloo.ras.ucalgary.ca>
On Thu, 6 Dec 2001 17:21:44 -0700
Richard Gooch <rgooch@ras.ucalgary.ca> wrote:
> I gave it as much testing as I could, but there comes a point where
> you don't get any more test reports (because people are lazy) where
> you have to throw it out for a pre-patch which *will* get testing.
> I got tired of begging for people to test it.
OK. Here I'm send me all you would like to get tested!
> Basic chicken and egg problem. It's the same reason Linus released
> 2.4.0-test* when it was really 2.3.99++.
I use devfs for years on workstations. I never had major problems, only
that ALSA needs a few days to follow changes, and some string
cripling when modprobe is called (solved for months) ...
[...]
> Anyway, this is all semantics and history. All that matters is that
> the latest code is much better, and I'm working on getting the last
> wrinkles out. We're still in a pre-patch, so no need to panic yet.
> I've been diligent about fixing things (mostly battling with
> incomplete bug reports).
I try to get more details (than I had in the last IDE one) into my next
reports - sorry ;-)
> Regards,
>
> Richard....
> Permanent: rgooch@atnf.csiro.au
> Current: rgooch@ras.ucalgary.ca
k33p h4ck1n6
René
--
René Rebe (Registered Linux user: #248718 <http://counter.li.org>)
eMail: rene.rebe@gmx.net
rene@rocklinux.org
Homepage: http://www.tfh-berlin.de/~s712059/index.html
Anyone sending unwanted advertising e-mail to this address will be
charged $25 for network traffic and computing time. By extracting my
address from this message or its header, you agree to these terms.
next prev parent reply other threads:[~2001-12-07 0:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ljcupnv.1ghotjk@ifi.uio.no>
2001-12-06 20:14 ` Jonathan Hudson
2001-12-06 21:30 ` Rene Rebe
2001-12-06 23:27 ` Greg KH
2001-12-06 23:37 ` Alexander Viro
2001-12-06 23:57 ` Rene Rebe
2001-12-07 0:09 ` Alexander Viro
2001-12-07 0:35 ` Rene Rebe [this message]
2001-12-07 0:20 ` Rene Rebe
2001-12-07 0:21 ` Richard Gooch
2001-12-06 23:45 ` Rene Rebe
2001-12-07 0:00 ` Greg KH
2001-12-07 0:11 ` Rene Rebe
2001-12-07 0:21 ` Greg KH
2001-12-06 20:01 kees
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=20011207013546.586f8948.rene.rebe@gmx.net \
--to=rene.rebe@gmx.net \
--cc=greg@kroah.com \
--cc=jonathan@daria.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®