From: Petr Baudis <pasky@suse.cz>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Wolfgang Denk <wd@denx.de>, Jon Smirl <jonsmirl@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: Licensing and the library version of git
Date: Thu, 27 Jul 2006 22:51:58 +0200 [thread overview]
Message-ID: <20060727205158.GE13776@pasky.or.cz> (raw)
In-Reply-To: <Pine.LNX.4.63.0607272239050.29667@wbgn013.biozentrum.uni-wuerzburg.de>
Hi,
Dear diary, on Thu, Jul 27, 2006 at 10:39:55PM CEST, I got a letter
where Johannes Schindelin <Johannes.Schindelin@gmx.de> said that...
> >From a standpoint of copyright (which the GPL relies on), this is not
> possible: you cannot include C code into Java. And if it is _translated_
> from C into Java, it is not copyrighted any more.
now that's a pretty strong statement - did a lawyer tell you that?
(Lawyer in what country? Germany?) Because copyrights are generally
retained over translations, otherwise I could freely publish
e.g. Czech translation of someone else's English book without any
permissions and such, which is obviously not the case.
There has been actually similar issue with OpenTTD - it was created by
translating Transport Tycoon Deluxe assembly to C without permission of
original TTD copyright owner (not that anyone actually knows for sure
who that is, after series of company mergers and buyouts). I don't think
anyone consulted a lawyer about legality of that either but I believe
that most people agree that this is basically illegal (but most likely,
noone will ever sue, or care at all).
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Snow falling on Perl. White noise covering line noise.
Hides all the bugs too. -- J. Putnam
next prev parent reply other threads:[~2006-07-27 20:52 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 21:36 Licensing and the library version of git Jon Smirl
2006-07-27 1:40 ` Shawn Pearce
2006-07-27 11:41 ` Petr Baudis
2006-07-27 12:02 ` Johannes Schindelin
2006-07-27 12:54 ` Jon Smirl
2006-07-27 13:11 ` Petr Baudis
2006-07-27 16:11 ` Jon Smirl
[not found] ` <Pine.LNX.4.64 .0607270936200.4168@g5.osdl.org>
2006-07-27 16:38 ` Johannes Schindelin
2006-07-27 16:41 ` Linus Torvalds
2006-07-27 16:46 ` Linus Torvalds
2006-07-27 16:58 ` Jakub Narebski
2006-07-27 17:47 ` Jon Smirl
2006-07-28 0:25 ` Anand Kumria
2006-07-27 16:51 ` Grzegorz Kulewski
2006-07-27 17:07 ` Linus Torvalds
2006-07-27 19:31 ` Daniel Barkalow
2006-07-27 20:41 ` Johannes Schindelin
2006-07-27 18:42 ` David Lang
2006-07-27 19:44 ` Linus Torvalds
2006-07-27 19:49 ` David Lang
2006-07-27 20:38 ` Johannes Schindelin
2006-07-28 0:24 ` Anand Kumria
2006-07-28 0:43 ` Jon Smirl
2006-07-28 9:01 ` Johannes Schindelin
2006-07-27 14:04 ` Johannes Schindelin
2006-07-27 17:20 ` Petr Baudis
2006-07-27 17:23 ` Petr Baudis
2006-07-27 17:44 ` Linus Torvalds
2006-07-27 19:56 ` Wolfgang Denk
2006-07-27 20:39 ` Johannes Schindelin
2006-07-27 20:51 ` Petr Baudis [this message]
2006-07-27 21:06 ` Johannes Schindelin
2006-07-27 21:10 ` Wolfgang Denk
2006-07-27 21:16 ` Johannes Schindelin
2006-07-27 21:15 ` Linus Torvalds
2006-07-27 21:19 ` Johannes Schindelin
2006-07-28 5:04 ` Shawn Pearce
2006-07-28 8:44 ` Johannes Schindelin
2006-07-29 3:56 ` Shawn Pearce
2006-07-29 4:31 ` Jon Smirl
2006-07-29 11:21 ` Johannes Schindelin
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=20060727205158.GE13776@pasky.or.cz \
--to=pasky@suse.cz \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=wd@denx.de \
/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;
as well as URLs for NNTP newsgroup(s).