From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: Jonathan Larmour <jlarmour@redhat.com>,
Andreas Schuldei <andreas@schuldei.org>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Whom to contact for licensing issues?
Date: Mon, 11 Dec 2000 14:58:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20001211175448.00b04ec0@larwe.com> (raw)
In-Reply-To: <3A35589E.CA7FC336@redhat.com>
Hi Jonathan,
> > Is there anyone (shure there is! Who is it?) both knowledgeable and
> > empowered concerning the ecos license?
>
>ecos-maintainers@redhat.com is the best place for such queries.
Would this also be the correct destination for inquiries related to
contribution legalistics?
I have some mass-storage and encryption code that I'd like to contribute,
that is really very generic and not at all proprietary, but happens to be
used in the product I work on in my day job. I am wondering about ways
around this issue.
=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/
next prev parent reply other threads:[~2000-12-11 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 14:32 Andreas Schuldei
[not found] ` <3A35589E.CA7FC336@redhat.com>
2000-12-11 14:58 ` Lewin A.R.W. Edwards [this message]
2000-12-12 10:55 ` 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=4.3.2.7.2.20001211175448.00b04ec0@larwe.com \
--to=larwe@larwe.com \
--cc=andreas@schuldei.org \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jlarmour@redhat.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).