From: Tim Hockin <thockin@sun.com>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH 1/4] fix NGROUPS hard limit (resend)
Date: Tue, 22 Oct 2002 10:44:48 -0700 [thread overview]
Message-ID: <3DB58E90.4020008@sun.com> (raw)
In-Reply-To: <20021022013928.GH25042@vitelus.com>
Aaron Lehmann wrote:
> On Mon, Oct 21, 2002 at 05:36:25PM -0700, Timothy Hockin wrote:
>
>>+ * 3. All advertising materials mentioning features or use of this software
>>+ * must display the following acknowledgement:
>>+ * This product includes software developed by the University of
>>+ * California, Berkeley and its contributors.
>
>
> Ahem.
>
> Since the copyright holder appears to be the Regents of the University
> of California, you have permission to remove this
> (ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change).
Done, in BK at the same URL. Thanks for the reference.
--
Tim Hockin
Systems Software Engineer
Sun Microsystems, Linux Kernel Engineering
thockin@sun.com
next prev parent reply other threads:[~2002-10-22 17:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 0:36 Timothy Hockin
2002-10-22 1:39 ` Aaron Lehmann
2002-10-22 17:44 ` Tim Hockin [this message]
2002-10-22 9:51 ` Alan Cox
2002-10-22 17:26 ` Tim Hockin
2002-10-22 17:45 ` Alan Cox
2002-10-22 17:37 ` Tim Hockin
2002-10-22 18:03 ` Jesse Pollard
2002-10-22 18:21 ` Tim Hockin
2002-10-22 18:54 ` Rik van Riel
2002-10-22 19:12 ` Jesse Pollard
2002-10-22 19:39 ` Rik van Riel
2002-10-25 9:34 ` Panu Matilainen
2002-10-25 12:49 ` jw schultz
2002-10-25 18:17 ` Tim Hockin
2002-10-22 19:45 ` Mike Touloumtzis
2002-10-22 20:13 ` Jesse Pollard
2002-10-22 20:30 ` Mike Touloumtzis
2002-10-23 14:17 ` Jesse Pollard
2002-10-22 20:18 ` Hildo.Biersma
2002-10-23 2:41 ` Simon Kirby
[not found] <354127220@toto.iv>
2002-10-23 0:09 ` Peter Chubb
2002-10-23 10:16 Randal, Phil
2002-10-29 19:32 Timothy Hockin
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=3DB58E90.4020008@sun.com \
--to=thockin@sun.com \
--cc=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome