From: Evan Martin <martine@danga.com>
To: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
Cc: caml <caml-list@inria.fr>, Jeff Henrikson <jehenrik@yahoo.com>,
Francois Rouaix <francois@rouaix.org>,
Kwluoto <kwluoto@mindspring.com>, Neilc <neilc@samurai.com>
Subject: [Caml-list] Re: Seattle OCaml SIG success
Date: Wed, 16 Jun 2004 12:27:57 -0700 [thread overview]
Message-ID: <20040616192757.GA30412@lulu> (raw)
In-Reply-To: <OOEALCJCKEBJBIJHCNJDKEOLHDAB.vanevery@indiegamedesign.com>
On Wed, Jun 16, 2004 at 12:00:00PM -0700, Brandon J. Van Every wrote:
> We had a good 1st meeting! Not sure what to call the group, maybe
> SOCaml? (pronounced "so camel") Or Scaml (pronounced "scam-l"). Or
> maybe these suck and you can think of better.
Camls, where the s is both for pluralization and for Seattle?
--
Evan Martin
martine@danga.com
http://neugierig.org
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
parent reply other threads:[~2004-06-17 6:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <OOEALCJCKEBJBIJHCNJDKEOLHDAB.vanevery@indiegamedesign.com>]
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=20040616192757.GA30412@lulu \
--to=martine@danga.com \
--cc=caml-list@inria.fr \
--cc=francois@rouaix.org \
--cc=jehenrik@yahoo.com \
--cc=kwluoto@mindspring.com \
--cc=neilc@samurai.com \
--cc=vanevery@indiegamedesign.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