From: Andrew Lunn <andrew.lunn@ascom.ch>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Jonathan Larmour <jifl@ecoscentric.com>,
Andrew Lunn <andrew@lunn.ch>,
eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: Update jffs2 from public MTD
Date: Wed, 18 Aug 2004 10:17:00 -0000 [thread overview]
Message-ID: <20040818101736.GK6981@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <1092822701.14552.428.camel@hades.cambridge.redhat.com>
On Wed, Aug 18, 2004 at 10:51:42AM +0100, David Woodhouse wrote:
> On Fri, 2004-08-13 at 13:30 +0100, Jonathan Larmour wrote:
> > Bart's just been telling me that he remembers David saying in the pub about
> > future JFFS2 contribs not being assigned. Sorry if I've forgotten that. So
> > is that still the case?
[..]
> You are correct -- since Red Hat IS pulled the plug on my servers
> without giving me even enough time to wind down the DNS expiry and move
> them to a new home, I stopped requiring copyright assignment. They no
> longer own CVS JFFS2.
Hi David
One thing to consider is maybe trying to get RedHat to contribute the
parts it owns to FSF when it transfers eCos. Would you be interested
in that? Would you be willing to require FSF copyright assingments for
jffs2?
Its something that must be acted on quickly if you think this is a
good idea. We would have to get assignments for the recent changes
which are not owned by RedHat.
Andrew
next prev parent reply other threads:[~2004-08-18 10:17 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
2004-08-13 12:30 ` Jonathan Larmour
2004-08-18 9:51 ` David Woodhouse
2004-08-18 10:17 ` Andrew Lunn [this message]
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=20040818101736.GK6981@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=andrew@lunn.ch \
--cc=dwmw2@infradead.org \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=jifl@ecoscentric.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 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).