From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: Mark Harig <idirectscm@aim.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: Welcome new contributor Mark Harig!
Date: Fri, 04 Mar 2011 21:28:21 +0000 [thread overview]
Message-ID: <87ipvy1sp6.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <m3ei6nfdkp.fsf@unquote.localdomain> (Andy Wingo's message of "Fri, 04 Mar 2011 10:19:02 +0100")
Andy Wingo <wingo@pobox.com> writes:
> Hey all,
>
> Let's welcome new contributor Mark Harig! Mark is interested in
> documentation, but who knows to what nooks and hollows of Guile the hack
> will lead. Welcome aboard, Mark!
Welcome indeed!
Neil
next prev parent reply other threads:[~2011-03-04 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 9:19 Welcome new contributor Mark Harig! Andy Wingo
2011-03-04 21:28 ` Neil Jerram [this message]
2011-03-05 2:44 ` Noah Lavine
2011-03-05 20:19 ` Mark Harig
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ipvy1sp6.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=idirectscm@aim.com \
--cc=wingo@pobox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).