From: Phil Schwan <pschwan@thepuffingroup.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] [Helge.Deller@ruhr-uni-bochum.de: licencing-question... ?]
Date: Fri, 9 Jul 1999 13:09:13 -0400 [thread overview]
Message-ID: <19990709130913.H14613@thepuffingroup.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 218 bytes --]
The mailing list is still grossly misbehaving, but it seems to only do
so for Helge's mail. I'm dealing with some mailing list issues today,
so I'll look at this as well. In the meantime, here's Helge's mail:
-Phil
[-- Attachment #2: Type: message/rfc822, Size: 2423 bytes --]
From: Helge Deller <Helge.Deller@ruhr-uni-bochum.de>
Cc: parisc-linux@thepuffingroup.com
Subject: licencing-question... ?
Message-ID: <37862832.63D6A751@ruhr-uni-bochum.de>
Hi !
Since my commits do not show on the cvs-parisc-list......
I committed again some changes (Phillip: I only changed some small things, so that we
could compile the source again; please ignore all my changes in irq.c !), but my
main-question is:
Are we/Am I allowed to use code from the OSF-parisc-port ???
The license from this port is:
-----------------------------------------------------------------
/*
* Copyright 1996 1995 by Open Software Foundation, Inc.
* All Rights Reserved
*
* Permission to use, copy, modify, and distribute this software and
* its documentation for any purpose and without fee is hereby granted,
* provided that the above copyright notice appears in all copies and
* that both the copyright notice and this permission notice appear in
* supporting documentation.
*
* OSF DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE
* INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
* FOR A PARTICULAR PURPOSE.
*
* IN NO EVENT SHALL OSF BE LIABLE FOR ANY SPECIAL, INDIRECT, OR
* CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
* LOSS OF USE, DATA OR PROFITS, WHETHER IN ACTION OF CONTRACT,
* NEGLIGENCE, OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
* WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*/
/*
* Copyright (c) 1990,1991,1994 The University of Utah and
* the Computer Systems Laboratory (CSL). All rights reserved.
*
* THE UNIVERSITY OF UTAH AND CSL PROVIDE THIS SOFTWARE IN ITS "AS IS"
* CONDITION, AND DISCLAIM ANY LIABILITY OF ANY KIND FOR ANY DAMAGES
* WHATSOEVER RESULTING FROM ITS USE.
*
* CSL requests users of this software to return to csl-dist@cs.utah.edu any
* improvements that they make and grant CSL redistribution rights.
*
*/
-----------------------------------------------------------------
Can we use the code, is it OK to accept this license, or shall we rewrite all ????
Thanks,
Helge.
next reply other threads:[~1999-07-09 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-09 17:09 Phil Schwan [this message]
1999-07-09 17:52 ` [parisc-linux] licencing-question... ? Matthew Wilcox
1999-07-18 19:17 ` Alan Cox
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=19990709130913.H14613@thepuffingroup.com \
--to=pschwan@thepuffingroup.com \
--cc=parisc-linux@thepuffingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.