From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>,
David Woodhouse <dwmw2@redhat.com>
Subject: Re: Update jffs2 from public MTD
Date: Fri, 13 Aug 2004 11:06:00 -0000 [thread overview]
Message-ID: <411CA0AC.9040307@eCosCentric.com> (raw)
In-Reply-To: <20040812213722.GV9839@lunn.ch>
Andrew Lunn wrote:
> Index: fs/jffs2/current/src/compr.c
> ===================================================================
> RCS file: /cvs/ecos/ecos/packages/fs/jffs2/current/src/compr.c,v
> retrieving revision 1.6
> diff -u -r1.6 compr.c
> --- fs/jffs2/current/src/compr.c 1 Apr 2004 03:17:57 -0000 1.6
> +++ fs/jffs2/current/src/compr.c 12 Aug 2004 21:29:23 -0000
> @@ -2,32 +2,39 @@
> * JFFS2 -- Journalling Flash File System, Version 2.
> *
> * Copyright (C) 2001-2003 Red Hat, Inc.
> - *
> * Created by Arjan van de Ven <arjanv@redhat.com>
> *
> + * Copyright (C) 2004 Ferenc Havasi <havasi@inf.u-szeged.hu>,
> + * University of Szeged, Hungary
> + *
Erk, this is slightly unexpected. IIRC JFFS2 isn't one of the things on the
list to be assigned by RH (goodness knows when at the current rate) to the
FSF (correct me if I'm misremembering!). But even so, it's an....
interesting development if copyright is to be shared liberally in future
and RH isn't going to be getting assignments for JFFS2 patches.
David, is this what JFFS2's policy for contributions now is? Or is this
just something in progress?
For example if eCos ever changes licence in the future, which is always a
possibility (I'm always fearful someone will find a workaround for the eCos
exception and we'll need to tighten the wording), then JFFS2 wouldn't be
able to change.
I'm not sure how much (if anything) of a problem this is, but we'd better
make sure we all know what the future status is going to be.
If we decide it is a problem, we could reverse this change and not import
any further JFFS2 code, but that does seem overkill.
Or more likely just put up with it, and deal with the consequences down the
road if we have to change licence and find that we can only use JFFS2 under
the full GPL.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next parent reply other threads:[~2004-08-13 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040812213722.GV9839@lunn.ch>
2004-08-13 11:06 ` Jonathan Larmour [this message]
2004-08-13 12:30 ` Jonathan Larmour
2004-08-18 9:51 ` David Woodhouse
2004-08-18 10:17 ` Andrew Lunn
2004-08-18 10:28 ` David Woodhouse
2004-08-18 12:44 ` Jonathan Larmour
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=411CA0AC.9040307@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=andrew@lunn.ch \
--cc=dwmw2@redhat.com \
--cc=ecos-maintainers@ecos.sourceware.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).