From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] u9fs re-release
Date: Fri, 6 Dec 2002 11:59:07 -0500 [thread overview]
Message-ID: <Pine.LNX.4.30.0212061157330.3978-101000@athena> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1574 bytes --]
In the event you don't already have one you like ...
1.2w /lib/face/48x48x4/j/j.1
!echo 'ssz.com/unknown j/j.1' >> /lib/face/48x48x4/.dict
I knew I'ld be able to contribute to the community somehow.
Sam
>
> On Thu, 5 Dec 2002, Russ Cox wrote:
>
> > > It strikes me as being very close, at least in intent, to the BSD
> > > licence. I concur with those who believe that having as few
> > > variations as possible from a small set of fundamental "Open Source"
> > > licences is good for the community in general and bad for lawyers,
> > > so in my opinion this particular licence should explicitly model
> > > itself on the BSD one.
> >
> > The point of this was NOT to reopen haggling over licensing.
> > Bell Labs has been using that boilerplate since before the term
> > "open source" existed. It's not like the wording was written from
> > scratch yesterday.
> >
> > Please please PLEASE don't continue this thread. We'll all just
> > have filled mailboxes and nothing useful to show for it.
>
> That's funny since you're the one who opened with a jab...
>
>
> --
> ____________________________________________________________________
>
> We don't see things as they are, ravage@ssz.com
> we see them as we are. www.ssz.com
> jchoate@open-forge.org
> Anais Nin www.open-forge.org
>
> --------------------------------------------------------------------
>
[-- Attachment #2.1: Type: text/plain, Size: 392 bytes --]
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Type: APPLICATION/OCTET-STREAM; NAME="j.1"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.4.30.0212061157280.3978@athena>
Content-Description:
Content-Disposition: ATTACHMENT; FILENAME="j.1"
[-- Attachment #2.2: j.1.suspect --]
[-- Type: application/octet-stream, Size: 2051 bytes --]
next reply other threads:[~2002-12-06 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 16:59 Sam [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-07 0:29 Geoff Collyer
2002-12-05 16:06 ozan s. yigit
2002-12-05 16:03 ozan s. yigit
2002-12-05 15:53 Russ Cox
2002-12-05 22:41 ` Jim Choate
2002-12-05 15:32 Russ Cox
2002-12-05 15:44 ` Lucio De Re
2002-12-05 23:19 ` Ronald G. Minnich
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=Pine.LNX.4.30.0212061157330.3978-101000@athena \
--to=sah@softcardsystems.com \
--cc=9fans@cse.psu.edu \
/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).