From: David Woodhouse <dwmw2@infradead.org>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: Jonathan Larmour <jifl@ecoscentric.com>,
eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: rbtree licence dilemma
Date: Tue, 21 Jan 2003 09:02:00 -0000 [thread overview]
Message-ID: <15706.1043139706@passion.cambridge.redhat.com> (raw)
In-Reply-To: <20030121084412.GE9033@biferten.ma.tech.ascom.ch>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
andrew.lunn@ascom.ch said:
> What about the re-licencing issue, assuming we decide to go that way.
> If you cannot convince some company to use the modGPL version of eCos
> and instead decide to offer a version with another licence, it will
> probably no longer be "free" and so this exception fails. I also
> guess, that since we don't hold the copywrite, we cannot change the
> license on this part anyway? So, it would have to be removed.
/me Googles... How about http://users.footprints.net/~kaz/kazlib.html ?
We'd need to contact the author and ask to make sure he wouldn't then want
_all_ users of it in eCos to mail him as described in the MUST_READ file
(attached), but I suspect that won't be a problem.
--
dwmw2
[-- Attachment #2: MUST_READ --]
[-- Type: text/plain , Size: 1141 bytes --]
Greetings, Programmer!
I gather that because you are reading this, you are probably considering using
the C language translation units included here in your own software. If that
is the case, I would like to know who you are and urge you to contact me.
Here is why: I rove over this code periodically looking for defects. In fact,
I use it in my own programming projects. If I discover a defect, I will
notify everyone who I know is a user of this software. If there is a serious
defect in some code that you are using in your software project, wouldn't you
want to be informed? In fact, there is no question that you _need_ to be
informed!
Here is what you do: simply send an e-mail message to kaz@ashi.footprints.net
with the subject "kazlib" and the body "I am a user". Be sure that your message
has a good return address. I will manually add your e-mail address to a list
which I will use only for the purpose of notifications regarding Kazlib. You
will receive a reply to the effect that you are added.
If ever you should wish to be removed from this list, simply ask and it shall
be done.
Yours in earnest,
Kaz Kylheku
next prev parent reply other threads:[~2003-01-21 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 1:16 Jonathan Larmour
2003-01-21 8:44 ` Andrew Lunn
2003-01-21 9:02 ` David Woodhouse [this message]
2003-01-21 10:11 ` Bart Veer
2003-01-21 10:33 ` David Woodhouse
2003-01-21 10:44 ` Bart Veer
2003-01-21 18:52 ` Jonathan Larmour
2003-01-21 19:31 ` David Woodhouse
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=15706.1043139706@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=andrew.lunn@ascom.ch \
--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).