From: Daniel Black <dragonheart@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] truecrypt licensing - bug #241650
Date: Sat, 28 Feb 2009 09:34:12 +1100 [thread overview]
Message-ID: <200902280934.13331.dragonheart@gentoo.org> (raw)
I've run out of interest to chase down the answer to the range of issues here.
Can someone with a few hours look trough all the info and see if truecrypt
license has improved to a situation where it is not putting the gentoo-
foundation or gentoo user's at risk.
If you could provide a fully cited reply on the bug report.
Next step? Gentoo Foundation lawyers?
Sorry for the lack of interest especially to all those who want to use
truecrypt in the time being.
Daniel Black
next reply other threads:[~2009-02-27 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 22:34 Daniel Black [this message]
2009-02-28 0:05 ` [gentoo-dev] truecrypt licensing - bug #241650 Ferris McCormick
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=200902280934.13331.dragonheart@gentoo.org \
--to=dragonheart@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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