From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, wip-manual-2, updated. release_1-9-9-85-g0a864be
Date: Fri, 16 Apr 2010 22:18:32 +0100 [thread overview]
Message-ID: <871vefumdz.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <m3sk6w1p33.fsf@pobox.com> (Andy Wingo's message of "Thu, 15 Apr 2010 21:40:48 +0200")
Andy Wingo <wingo@pobox.com> writes:
> Hi Neil,
Hi Andy,
> I also think that wip-manual-2 is looking great! Your commit granularity
> is also really nice.
Thanks.
>>From my perspective each commit is ready! Why not just merge now? It's
> getting monotonically better :)
OK, I'll do that; thanks for the suggestion. For the sake of
explanation: I guess when I started wip-manual-2 I wasn't totally sure
that my direction was correct, or that it would meet with approval. But
given that it does, I agree that it makes sense now to continue in
master.
> That way when someone writes new docs, they have a better idea about how
> that fits in. For example I need to write something about "nil", and
> I'll look at your branch and see where you're going, but if it were
> merged already I could just look at the state of master and see where
> the right place would be.
Yes, absolutely.
> I still think it's the right statement to make :) Guile _is_ and _has_
> other things as well, but fundamentally it's a Scheme. IMO at least :)
Agreed. Historically and philosophically that's clearly true. And from
a practical point of view, however many other languages we support,
Scheme will always remain special because the compiler itself is written
in Scheme.
Regards,
Neil
prev parent reply other threads:[~2010-04-16 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1O0l18-0003HJ-PM@vcs-noshell.in.savannah.gnu.org>
2010-04-11 23:13 ` [Guile-commits] GNU Guile branch, wip-manual-2, updated. release_1-9-9-85-g0a864be Ludovic Courtès
2010-04-12 0:15 ` Neil Jerram
2010-04-12 8:23 ` Ludovic Courtès
2010-04-15 19:40 ` Andy Wingo
2010-04-16 21:18 ` Neil Jerram [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=871vefumdz.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--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).