From: Cesare Leonardi <celeonar@ngi.it>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Fix warning in fs/xfs.c
Date: Mon, 21 Jul 2008 23:40:07 +0200 [thread overview]
Message-ID: <48850237.6050700@ngi.it> (raw)
In-Reply-To: <87prp8ie41.fsf@xs4all.nl>
Marco Gerards wrote:
> Pavel Roskin <proski@gnu.org> writes:
>
>> On Thu, 2008-07-03 at 20:21 +0200, Marco Gerards wrote:
>>> Pavel Roskin <proski@gnu.org> writes:
>>>
>>>> ChangeLog:
>>>> * fs/xfs.c (struct grub_xfs_dir_header): Use names similar to
>>>> those in Linux XFS code. Provide a way to access 64-bit parent
>>>> inode.
>>>> (grub_xfs_iterate_dir): Use the new names. Avoid reading past
>>>> the end of struct grub_xfs_dir_header.
>>> *please* do not look at Linux code or whatever *and* contribute to
>>> GRUB. It might cause copyright troubles I will have to deal with :-/
>> I just tried to make names similar without copying any code. But it's a
>> useful reminder.
>
> What I meant is that even *looking* at code might cause problems.
> People can claim you have stolen their ideas. That would essentially
> mean the same as copying code. I just want to avoid such problems at
> beforehand.
But one of the best aspect of the free software is exactly that you
could look inside other's code and reuse it and its ideas.
Would be a problem if you look the source of a program covered by NDA,
or by some other closed license, but with Linux kernel?? If you couldn't
look inside a GPL2 project then it would be a loss of the free software
and the GPL3. And you have to reinvent something that others has already
done well...
Furthermore, AFAIK, the problem of protecting code implementation is
covered by copyright, while protecting ideas is a patent job. Now, Linux
is GPL2 and it's not encumbered by patents, so what's the problem?
Regards.
Cesare.
prev parent reply other threads:[~2008-07-21 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 0:10 [PATCH] Fix warning in fs/xfs.c Pavel Roskin
2008-07-03 18:21 ` Marco Gerards
2008-07-03 18:48 ` Pavel Roskin
2008-07-20 18:50 ` Marco Gerards
2008-07-20 20:28 ` Pavel Roskin
2008-07-21 21:40 ` Cesare Leonardi [this message]
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=48850237.6050700@ngi.it \
--to=celeonar@ngi.it \
--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.