From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: John Levon <moz@compsoc.man.ac.uk>
Cc: alan@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tainting FAQ
Date: Thu, 11 Oct 2001 12:08:21 -0600 [thread overview]
Message-ID: <200110111808.f9BI8Ls04654@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <20011011184241.A95852@compsoc.man.ac.uk>
In-Reply-To: <20011011184241.A95852@compsoc.man.ac.uk>
John Levon writes:
> short and sweet. (useful) comments ?
Maybe we're giving out too much information? To put it bluntly, if
people are told what we're up to, they'll doctor the bug reports.
People are selfish and will try to game the system. I'm not even sure
if we should expose the term "tainted" in the first place. Maybe a
"compatibility bitmask" with a hex value should be reported instead.
Alan: you're the instigator of this scheme. How widely do you want to
publish what this is really about? I note that lwn.net had a paragraph
on the tainting scheme.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-10-11 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 17:42 John Levon
2001-10-11 18:08 ` Richard Gooch [this message]
2001-10-11 19:44 ` Alan Cox
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=200110111808.f9BI8Ls04654@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moz@compsoc.man.ac.uk \
/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®