From: wkt@minnie.tuhs.org (Warren Toomey)
Subject: [TUHS] Re: [pups] Re: Caldera license
Date: Fri, 25 Jan 2002 08:05:31 +1000 (EST) [thread overview]
Message-ID: <200201242205.g0OM5V212564@minnie.tuhs.org> (raw)
In-Reply-To: <3C502BA9.5040701@pacbell.net> from Michael Davidson at "Jan 24, 2002 07:43:37 am"
In article by Michael Davidson:
> I believe that it is sufficient to provide a single copy of the license
> / copyright text from the letter along with any file or files that
> either come directly from or are derived from
> any of the listed operating systems.
I believe that's all we need to do. I'm only going to have 1 copy
of the license agreement in the Unix Archive, with the odd pointer
to it in some of the READMEs.
Warren
prev parent reply other threads:[~2002-01-24 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <23C0CD62-10D1-11D6-A66D-000502F91E77@uwlax.edu>
2002-01-24 14:17 ` [TUHS] " Warren Toomey
2002-01-24 15:13 ` [TUHS] Re: [pups] " Bill Gunshannon
2002-01-24 15:43 ` Michael Davidson
2002-01-24 22:05 ` Warren Toomey [this message]
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=200201242205.g0OM5V212564@minnie.tuhs.org \
--to=wkt@minnie.tuhs.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;
as well as URLs for NNTP newsgroup(s).