From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Enable writing to ATA devices, fix several bugs
Date: Mon, 21 Jul 2008 17:53:01 +0200 [thread overview]
Message-ID: <87zlobgroi.fsf@xs4all.nl> (raw)
In-Reply-To: <1216654885.3460.21.camel@dv> (Pavel Roskin's message of "Mon, 21 Jul 2008 11:41:25 -0400")
Pavel Roskin <proski@gnu.org> writes:
> On Mon, 2008-07-21 at 17:20 +0200, Marco Gerards wrote:
>> Javier Martín <lordhabbit@gmail.com> writes:
>>
>> > So what? Aren't both Linux and GRUB under the GPL? That _should_ mean
>> > that we can look at their code and put it into GRUB ("create a
>> > derivative work") either as-is or modified.
>>
>> For GRUB 2 we require copyright assignments.
>
> Also, Linux is under GPLv2 and GRUB is under GPLv3. This means that
> Linux developers could object that their code is restricted further than
> GPLv2 allows, e.g. there are additional anti-DRM provisions that the
> recipients of the GRUB code has to fulfill.
>
> That said, I cannot imagine that copying of variable names could be
> treated as a copyright violation. For instance, Wine reimplements
> Windows API, and they just have to use the same names.
Please do not put words in my mouth, that is not what I said. I said
looking at Linux *code* should be avoided. If you have a look at the
ATA *code*, you might copy their algorithms or whatever. I am asking
you to be careful. Looking at code might give you an idea about how
to solve a problem, you might even implement this and legally... well,
I am not sure when you violate copyright or when not. I cannot tell
if you looked at their code if you opened the files, study the
variable names and how they are used.
--
Marco
next prev parent reply other threads:[~2008-07-21 15:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 0:17 [PATCH] Enable writing to ATA devices, fix several bugs Pavel Roskin
2008-07-03 14:10 ` Robert Millan
2008-07-03 18:27 ` Marco Gerards
2008-07-03 20:50 ` Pavel Roskin
2008-07-04 11:50 ` Marco Gerards
2008-07-04 17:07 ` Pavel Roskin
2008-07-20 18:55 ` Marco Gerards
2008-07-20 20:24 ` Pavel Roskin
2008-07-21 12:49 ` Marco Gerards
2008-07-21 13:19 ` Javier Martín
2008-07-21 15:20 ` Marco Gerards
2008-07-21 15:33 ` Javier Martín
2008-07-21 15:56 ` Marco Gerards
2008-07-21 15:41 ` Pavel Roskin
2008-07-21 15:53 ` Marco Gerards [this message]
2008-07-21 16:00 ` Pavel Roskin
2008-07-21 16:10 ` Marco Gerards
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=87zlobgroi.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.