From: Matt Gushee <matt@gushee.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] LablGTK list working?
Date: Wed, 03 May 2006 16:09:23 -0600 [thread overview]
Message-ID: <44592A13.9090403@gushee.net> (raw)
In-Reply-To: <20060504065002.257b9fda.ocaml-erikd@mega-nerd.com>
Erik de Castro Lopo wrote:
>> I thought I would join the LablGTK mailing list; I sent an e-mail
> I joined that list about 3 weeks ago. The lists subscriptions are done
> manually by Jacques Garrigue (lastname@math.nagoya-u.ac.jp) so sometimes
> this takes a little more time than people are used to :-).
Oh, okay, thanks. I suppose his university won't let him install Mailman
or any other good list manager (I spent some time working at a Japanese
university, and their IT departments tend to be very, well ...
conservative, to put it politely).
--
Matt Gushee
The Reluctant Geek: http://matt.gushee.net/rg/
prev parent reply other threads:[~2006-05-03 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 20:28 Matt Gushee
2006-05-03 20:50 ` [Caml-list] " Erik de Castro Lopo
2006-05-03 22:09 ` Matt Gushee [this message]
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=44592A13.9090403@gushee.net \
--to=matt@gushee.net \
--cc=caml-list@inria.fr \
/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).