From: "Benjamin Huntsman" <BHuntsman@mail2.cu-portland.edu>
To: <9fans@9fans.net>
Subject: Re: [9fans] 2nd Edition
Date: Tue, 19 Aug 2008 09:04:49 -0700 [thread overview]
Message-ID: <621112A569DAE948AD25CCDCF1C075331AB346@dolly.ntdom.cupdx> (raw)
In-Reply-To: <621112A569DAE948AD25CCDCF1C075331AB345@dolly.ntdom.cupdx>
>this setup reminds me of the story about the priest who, playing golf
>against the orders of his superiors on sunday morning, hits a hole in one.
ouch.
>supposing you're successful in getting a licence and you do great things
>with the next port. who are you going to tell?
>
>- erik
Does the license prevent updating the port as well??
next parent reply other threads:[~2008-08-19 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a9b073dfb717cea36476a6f2086f56c9@quanstro.net>
[not found] ` <621112A569DAE948AD25CCDCF1C075331AB345@dolly.ntdom.cupdx>
2008-08-19 16:04 ` Benjamin Huntsman [this message]
2008-08-19 16:28 ` erik quanstrom
2008-08-19 16:58 ` ron minnich
2008-08-19 17:18 ` John Waters
2008-08-19 12:57 erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2008-08-18 21:15 Benjamin Huntsman
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=621112A569DAE948AD25CCDCF1C075331AB346@dolly.ntdom.cupdx \
--to=bhuntsman@mail2.cu-portland.edu \
--cc=9fans@9fans.net \
/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).