From: Philipp Rumpf <prumpf@suse.de>
To: Mike Hibler <mike@fast.cs.utah.edu>
Cc: Helge.Deller@ruhr-uni-bochum.de, shaver@netscape.com,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Helge's commits
Date: Mon, 12 Jul 1999 07:00:12 +0200 [thread overview]
Message-ID: <19990712070012.A10285@suse.de> (raw)
In-Reply-To: <199907120440.WAA09953@fast.cs.utah.edu>; from Mike Hibler on Sun, Jul 11, 1999 at 10:40:05PM -0600
> Doh! You are right, we do have quite a few files in there with the
> notorious advertising clause. I assume that is the sticky part?
> I'll see what I can do...
Don't waste your time. The first thing to do is too check with OSF. I guess
their response will be "No way" so we can forget about that.
next prev parent reply other threads:[~1999-07-12 4:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-12 4:40 [parisc-linux] Helge's commits Mike Hibler
1999-07-12 5:00 ` Philipp Rumpf [this message]
1999-07-12 5:20 ` Jeffrey A Law
[not found] <199907101141.FAA25297@puffin.external.hp.com>
1999-07-10 22:46 ` Philipp Rumpf
1999-07-11 9:36 ` Helge Deller
1999-07-11 22:36 ` Mike Shaver
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=19990712070012.A10285@suse.de \
--to=prumpf@suse.de \
--cc=Helge.Deller@ruhr-uni-bochum.de \
--cc=mike@fast.cs.utah.edu \
--cc=parisc-linux@thepuffingroup.com \
--cc=shaver@netscape.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox