From: Tavis Ormandy <taviso@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Which license?
Date: Thu, 27 Apr 2006 20:19:47 +0100 [thread overview]
Message-ID: <20060427191947.GA31434@sdf.lonestar.org> (raw)
In-Reply-To: <Pine.BSO.4.58.0604271419090.8377@ida.bway.net>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On Thu, Apr 27, 2006 at 02:21:38PM -0400, A. Khattri wrote:
> ## This software may be freely copied, modified and redistributed
> ## without fee for non-commerical purposes provided that this license
> ## remains intact and unmodified with any distribution.
>
> Last time I looked, there were some 800 or so files in
> /usr/portage/license/ - so which one would I use?
free-noncomm looks like a good match.
--
-------------------------------------
taviso@sdf.lonestar.org | finger me for my pgp key.
-------------------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 300 bytes --]
next prev parent reply other threads:[~2006-04-27 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 18:21 [gentoo-dev] Which license? A. Khattri
2006-04-27 18:50 ` Donnie Berkholz
2006-04-27 19:03 ` Chris Gianelloni
2006-04-27 19:09 ` Albert Hopkins
2006-04-27 19:19 ` Tavis Ormandy [this message]
2006-04-27 19:32 ` Alin Nastac
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=20060427191947.GA31434@sdf.lonestar.org \
--to=taviso@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