From: <Hell.Surfers@cwctv.net>
To: jbradford@dial.pipex.com, mingo@elte.hu, mingo@elte.hu,
linux-kernel@vger.kernel.org
Subject: RE: BK MetaData License Problem?
Date: Mon, 7 Oct 2002 01:11:29 +0100 [thread overview]
Message-ID: <0ea2511110007a2DTVMAIL6@smtp.cwctv.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
The file must be available for free, seperately if its not poss to include it, the source must say its a GPL, thats about it.
Cheers, Dean McEwan. Currently hacking KGI, which I don't understand, oh and ask me about OpenModemTalk...
On Sun, 6 Oct 2002 15:23:38 +0100 (BST) jbradford@dial.pipex.com wrote:
[-- Attachment #2: Type: message/rfc822, Size: 2183 bytes --]
From: jbradford@dial.pipex.com
To: mingo@elte.hu
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: BK MetaData License Problem?
Date: Sun, 6 Oct 2002 15:23:38 +0100 (BST)
Message-ID: <200210061423.g96ENcH3003097@darkstar.example.net>
>
> until now the Linux kernel tree was distributed in a tarball that had a
> nice COPYING file in a very prominent spot. With BK the situation is
> different - and like i said in previous mails it's not BK's "fault", but
> BK's "effect" - and it's a situation that needs to be remedied, right?
Strictly speaking, isn't it a violation of the GPL for somebody to distribute a single file of any GPLed project, without attaching the COPYING file to it?
E.G. say somebody makes a CVS tree available via the web - you can download foobar.c without ever seeing the COPYING file.
John.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2002-10-07 0:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 0:11 Hell.Surfers [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-06 12:40 BK MetaData License Problem? Manfred Spraul
2002-10-06 13:13 ` Ingo Molnar
2002-10-06 15:48 ` Marek Habersack
2002-10-06 16:26 ` Manfred Spraul
2002-10-06 19:11 ` Marek Habersack
2002-10-06 16:29 ` Alan Cox
2002-10-06 16:22 ` Larry McVoy
2002-10-06 10:59 New BK " David S. Miller
2002-10-06 12:04 ` BK MetaData " Ingo Molnar
2002-10-06 11:52 ` David S. Miller
2002-10-06 12:18 ` jbradford
2002-10-06 12:35 ` jw schultz
2002-10-06 12:18 ` Ingo Molnar
2002-10-06 16:18 ` Daniel Berlin
2002-10-06 13:48 ` Russell King
2002-10-06 14:10 ` Ingo Molnar
2002-10-06 14:08 ` Russell King
2002-10-06 16:58 ` Alan Cox
2002-10-06 17:06 ` jbradford
2002-10-06 19:12 ` Marek Habersack
2002-10-06 14:23 ` jbradford
2002-10-06 19:39 ` Linus Torvalds
2002-10-06 20:00 ` Ingo Molnar
2002-10-06 22:52 ` Larry McVoy
2002-10-07 6:08 ` Ingo Molnar
2002-10-07 6:07 ` Larry McVoy
2002-10-06 17:17 ` Jes Sorensen
2002-10-06 17:38 ` Larry McVoy
2002-10-06 17:41 ` Alan Cox
2002-10-06 17:45 ` Jes Sorensen
2002-10-06 22:49 ` Larry McVoy
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=0ea2511110007a2DTVMAIL6@smtp.cwctv.net \
--to=hell.surfers@cwctv.net \
--cc=jbradford@dial.pipex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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