From: Andy Wingo <wingo@pobox.com>
To: Roland Orre <roland.orre@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: who wrote guile?
Date: Thu, 26 May 2011 22:36:56 +0200 [thread overview]
Message-ID: <m3zkm9p5av.fsf@unquote.localdomain> (raw)
In-Reply-To: <BANLkTim8w1R+ZvebQmtT7rcMfqKGYDt5zQ@mail.gmail.com> (Roland Orre's message of "Thu, 26 May 2011 22:15:59 +0200")
Hi Roland,
On Thu 26 May 2011 22:15, Roland Orre <roland.orre@gmail.com> writes:
> Not to forget where the raw-material came from, i.e. Aubrey Jaffer's scm
> http://www.galassi.org/mark//mydocs/guile-programmer_6.html
Of course Aubrey Jaffer's work was very important to Guile. I think
that we have mentioned this appropriately in the manual, but if you have
any specific suggestion on how things should be improved, do let us
know!
Happy hacking,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-05-26 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 20:01 who wrote guile? Andy Wingo
2011-05-26 20:15 ` Roland Orre
2011-05-26 20:36 ` Andy Wingo [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
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=m3zkm9p5av.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=roland.orre@gmail.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).