From: tytso@mit.edu
To: Evgeniy Ivanov <lolkaantimat@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Using parts of ext2_fs.h in BSD licensed code
Date: Mon, 15 Mar 2010 14:23:38 -0400 [thread overview]
Message-ID: <20100315182338.GG4484@thunk.org> (raw)
In-Reply-To: <e1e08eb01003151026q1352c02btf12d7cd6d84c3f21@mail.gmail.com>
On Mon, Mar 15, 2010 at 08:26:16PM +0300, Evgeniy Ivanov wrote:
> Just found, that recently FreeBSD got this:
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/fs/ext2fs/ext2fs.h
> It looks like I can easily include it to the BSD-licensed project and
> no GPL violation. But I dunno how did they wrote ext2fs.h, since it
> still must be based on ext2_fs.h
Constants and code points aren't subject to copyright, so they don't
have ask any question. The places where things start to get dicy is
with inline function and CPP macros, especially when the code starts
become non-trivial. i.e., there's only one way to do "(foo & MASK) !=
0", so that's probably not subject to copyright. A complicated 20
line function, even if it's in a header file, is probably going to be
subject to copyright. What is and isn't a matter of copyright is
something you'd have to get a lawyer to answer for you.
You can of couse also request permission, but that can get tricky,
especially if the person who originally wrote it can't easily be
tracked down (I haven't talked or e-mailed with Remy in years), or if
it was done by someone while being paid by their employer, in which
case some corporate lawyers might have to be dragged in to give
permission.
Fortunately I don't think there's much in the way of complicated code
in the header files that you would have to deal with.
Best regards,
- Ted
next prev parent reply other threads:[~2010-03-15 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 16:42 Using parts of ext2_fs.h in BSD licensed code Evgeniy Ivanov
2010-03-15 17:26 ` Evgeniy Ivanov
2010-03-15 18:23 ` tytso [this message]
2010-03-16 12:34 ` Evgeniy Ivanov
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=20100315182338.GG4484@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=lolkaantimat@gmail.com \
/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.