From: Andy Wingo <wingo@pobox.com>
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Some guile-unify activities
Date: Tue, 10 May 2011 11:15:37 +0200 [thread overview]
Message-ID: <m339km6hmu.fsf@unquote.localdomain> (raw)
In-Reply-To: <BANLkTimRfcdK7dH-sfsiWy7-gYUe-KuKRQ@mail.gmail.com> (Stefan Israelsson Tampe's message of "Tue, 10 May 2011 11:00:00 +0200")
On Tue 10 May 2011 11:00, Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:
> It's better to code and loose then never code at all
Yes!
> jokes aside, I'll will take this in small smelling shebackas. Main point is not me
> coding, the main point is to get this question moving :-)
Cool. Happy hacking!
A
--
http://wingolog.org/
prev parent reply other threads:[~2011-05-10 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 21:18 Some guile-unify activities Stefan Israelsson Tampe
2011-05-06 21:26 ` Noah Lavine
2011-05-08 15:38 ` Ludovic Courtès
2011-05-08 15:52 ` Andy Wingo
2011-05-09 11:15 ` Stefan Israelsson Tampe
2011-05-09 12:42 ` Andy Wingo
2011-05-09 18:35 ` Stefan Israelsson Tampe
2011-05-09 21:46 ` Andy Wingo
2011-05-10 9:00 ` Stefan Israelsson Tampe
2011-05-10 9:15 ` 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=m339km6hmu.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=stefan.itampe@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).