public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Alexander Viro <viro@math.psu.edu>, Aaron Lehmann <aaronl@vitelus.com>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
	adam@yggdrasil.com, linux-kernel@vger.kernel.org
Subject: Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h
Date: Fri, 25 May 2001 14:44:46 +0200	[thread overview]
Message-ID: <20010525144446.A15304@bug.ucw.cz> (raw)
In-Reply-To: <20010524230321.B23155@vitelus.com> <Pine.GSO.4.21.0105250229220.24864-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0105250229220.24864-100000@weyl.math.psu.edu>; from Alexander Viro on Fri, May 25, 2001 at 02:34:05AM -0400

Hi!

> > explicit about defining source code:
> > 	The source code for a work means the preferred form of the work for
> > 	making modifications to it.
> 
> Erm... May I point you to the sysdep/libm-ieee754/e_j0.c? There's a bunch
> of constants of unknown origin. If you want to modify the implementation
> you most certainly want more than numeric values.
> 
> Same goes for any tables that contain anything besides well-known constants.

Imagine the hell opening when you generate table of random numbers
with hardware generator :-). How do you write source of hardware
random generator?
								Pavel
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org

  parent reply	other threads:[~2001-05-27  0:01 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200105250559.f4P5x80365151@saturn.cs.uml.edu>
2001-05-25  6:03 ` Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h Aaron Lehmann
2001-05-25  6:34   ` Alexander Viro
2001-05-25  6:42     ` Aaron Lehmann
2001-05-25  6:58       ` Alexander Viro
2001-05-25  7:02       ` Andreas Jaeger
2001-05-25  7:05         ` Alexander Viro
2001-05-25 10:56     ` Erik Mouw
2001-05-25 11:56       ` Alexander Viro
2001-05-25 12:44     ` Pavel Machek [this message]
2001-05-29  1:38 Adam J. Richter
  -- strict thread matches above, loose matches on Subject: below --
2001-05-26 11:09 Adam J. Richter
2001-05-26  3:10 Adam J. Richter
2001-05-26 11:00 ` James Sutherland
2001-05-29  0:03   ` Jamie Lokier
2001-05-29  0:24     ` Alan Cox
2001-05-29  0:55       ` Jamie Lokier
2001-05-26  2:34 Adam J. Richter
2001-05-26  2:38 ` Larry McVoy
2001-05-26  4:52 ` Jeff V. Merkey
2001-05-25 17:02 Adam J. Richter
2001-05-25 17:23 ` Jacob Luna Lundberg
2001-05-25 18:30 ` Larry McVoy
2001-05-25 22:30   ` Aaron Lehmann
2001-05-26  1:43     ` Larry McVoy
2001-05-25 19:14 ` Doug Ledford
2001-05-25 10:36 Adam J. Richter
2001-05-25  9:34 Adam J. Richter
2001-05-25 16:06 ` Doug Ledford
     [not found] <mailman.990765360.7016.linux-kernel2news@redhat.com>
2001-05-25  6:02 ` Pete Zaitcev
     [not found] <Pine.BSF.4.21.0105242155540.4849-100000@beppo.feral.com>
2001-05-25  5:57 ` Aaron Lehmann
2001-05-25  6:26   ` Matthew Jacob
2001-05-25  6:31     ` Aaron Lehmann
2001-05-25  4:34 Aaron Lehmann
2001-05-25  5:07 ` Greg KH
2001-05-25 10:00 ` John Cavan
2001-05-25 11:10   ` Alan Cox
2001-05-25 16:17 ` 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=20010525144446.A15304@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=aaronl@vitelus.com \
    --cc=acahalan@cs.uml.edu \
    --cc=adam@yggdrasil.com \
    --cc=linux-kernel@vger.kernel.org \
    --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