From: Peter Samuelson <peter@cadcamlab.org>
To: Christopher Friesen <cfriesen@nortelnetworks.com>
Cc: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>,
linux-kernel@vger.kernel.org
Subject: Re: Fasttrak100 questions...
Date: Fri, 1 Dec 2000 21:44:15 -0600 [thread overview]
Message-ID: <20001201214415.E25464@wire.cadcamlab.org> (raw)
In-Reply-To: <8voa7g$d1r$1@forge.tanstaafl.de> <Pine.LNX.4.21.0011291152500.5109-100000@sol.compendium-tech.com> <20001129210830.J17523@forge.tanstaafl.de> <20001129165236.A9536@vger.timpanogas.org> <3A266EE7.4C734350@nortelnetworks.com>
In-Reply-To: <3A266EE7.4C734350@nortelnetworks.com>; from cfriesen@nortelnetworks.com on Thu, Nov 30, 2000 at 10:14:47AM -0500
[Christopher Friesen]
> I think you should re-read the GPL. You only have to provide source
> to people to whome you have distributed your new binaries, and you
> only have to provide that source if you are asked for it.
Oh, and you have to provide the complete text of the GPL as well, and
for that you do *not* have a "only if they ask for it" clause.
Or so it seems to some people, like RMS. See this week's DWN: there is
a nice long discussion in debian-devel about this. Apparently RMS
demands that all GPL'd Debian binary packages include a copy -- it is
not enough that the Debian base system already has a copy and that all
GPL'd source tarballs include a copy.
I do not agree with this interpretation, because it would mean that any
GPL'd file that can possibly be independently downloaded (such as a .c
file from a CVS server) must include that same 17k document.
...But just so everyone knows: according to RMS, every file on your FTP
server that you provide under the GPL v2 must include a copy of the
GPL. (Easy enough to do with tar files, harder for other formats, and
never mind the wasted bandwidth.) Having the GPL in a separate file on
your site does not count, apparently.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-02 4:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 22:46 Fasttrak100 questions James Lamanna
2000-11-25 1:35 ` Andre Hedrick
2000-11-25 12:10 ` Henning P. Schmiedehausen
2000-11-25 17:20 ` Andre Hedrick
2000-11-25 17:22 ` Andre Hedrick
2000-11-29 19:53 ` Dr. Kelsey Hudson
2000-11-29 20:08 ` Henning P . Schmiedehausen
2000-11-29 21:11 ` Andre Hedrick
2000-11-29 22:12 ` Stop your abusive language! (Re: Fasttrak100 questions...) Dominik Kubla
2000-11-29 23:52 ` Fasttrak100 questions Jeff V. Merkey
2000-11-30 15:14 ` Christopher Friesen
2000-11-30 18:43 ` Jeff V. Merkey
2000-11-30 18:09 ` Christopher Friesen
2000-11-30 20:10 ` Jeff V. Merkey
2000-12-02 3:44 ` Peter Samuelson [this message]
2000-12-03 22:54 ` Pavel Machek
2000-12-05 4:10 ` Peter Samuelson
2000-11-29 20:42 ` Alan Cox
2000-11-29 21:05 ` Andre Hedrick
2000-11-29 21:10 ` James A Sutherland
2000-11-29 21:18 ` Alan Cox
2000-11-29 21:30 ` Andre Hedrick
2000-12-02 16:50 ` Pavel Machek
2000-12-02 17:18 ` Alan Cox
2000-12-02 23:46 ` Theodore Y. Ts'o
2000-12-03 1:21 ` Jeff V. Merkey
2000-12-03 1:31 ` Jeff V. Merkey
2000-12-03 3:42 ` Theodore Y. Ts'o
2000-12-03 5:11 ` Jeff V. Merkey
2000-12-05 7:07 ` Brian F. G. Bidulock
2000-12-05 8:25 ` Jeff V. Merkey
-- strict thread matches above, loose matches on Subject: below --
2000-12-03 16:41 Wayne.Brown
2000-12-03 17:49 ` Pavel Machek
2000-12-03 18:45 ` 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=20001201214415.E25464@wire.cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=cfriesen@nortelnetworks.com \
--cc=jmerkey@vger.timpanogas.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