From: Jani Monoses <jani@iv.ro>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: ecos-maintainers@sources.redhat.com
Subject: Re: [RFC] lwip officially in ecos?
Date: Fri, 12 Sep 2003 14:34:00 -0000 [thread overview]
Message-ID: <20030912172217.46ded8c2.jani@iv.ro> (raw)
In-Reply-To: <3F61D493.7070900@eCosCentric.com>
On Fri, 12 Sep 2003 15:13:39 +0100
Jonathan Larmour <jifl@eCosCentric.com> wrote:
> Jani Monoses wrote:
> > Hello all
> >
> > I'd like to ask the maintainers' opinion on putting lwIP in ecos
> > CVS. I'm prepared to do all the legwork if the answer is positive.
> > lwIP is BSD-licensed and almost 'well-established' as the patch
> > submission doc requests. Although I intend to sign a copyright
> > assignment for other future contributions to ecos, IMO lwip is
> > unaffected because it is a separate BSD project but more importantly
> > because my contributions to it are minimal and quite a few people
> > worked on it (not as many as on the BSD stack or microwindows but
> > still)
>
> I'm all for it. I do agree it is well-established enough to waive the
> assignment for lwip itself. Of course changes to things outside of the
> lwIP package itself may be a different story.
The only changes outside the package are to io/eth/lwip which is already
in ecos.
A couple of clarifications about the submission:
- files in lwip have a BSD copyright text. I suppose there's no need to
add the ecos copyrigth text in each of them right?
- should I send a gzipped patch to ecos-patches or post a link to an EPK
(~200K)?
Jani
next prev parent reply other threads:[~2003-09-12 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 9:26 Jani Monoses
2003-09-12 10:19 ` Andrew Lunn
2003-09-12 10:25 ` Jani Monoses
2003-09-12 14:13 ` Jonathan Larmour
2003-09-12 14:34 ` Jani Monoses [this message]
2003-09-12 15:16 ` 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=20030912172217.46ded8c2.jani@iv.ro \
--to=jani@iv.ro \
--cc=ecos-maintainers@sources.redhat.com \
--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).