From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile User List <guile-user@gnu.org>
Subject: Re: A few patches for guile-www
Date: Fri, 26 Nov 2010 08:10:55 +0100 [thread overview]
Message-ID: <878w0glfuo.fsf@ambire.localdomain> (raw)
In-Reply-To: <87eia8orb6.fsf@ossau.uklinux.net> (Neil Jerram's message of "Fri, 26 Nov 2010 00:35:09 +0000")
Hi Neil,
() Fri, 26 Nov 2010 00:35:09 +0000
I've got back to some modlisp hacking, and as part of that have
rebased to guile-www-2.28.
Cool.
To get things working, in particular the modlisp support, I had
to make a few small changes, so I attach those for your
consideration. I think they're all self-evident, but of course
please ask if not.
Thanks; i appreciate the feedback. I have the impression after a
quick skim that all the changes are bugfixes (not merely enhancements).
Is that correct?
In any case, i will gladly apply them once i figure out
their nature and suitable ChangeLog entries.
thi
next prev parent reply other threads:[~2010-11-26 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 0:35 A few patches for guile-www Neil Jerram
2010-11-26 7:10 ` Thien-Thi Nguyen [this message]
2010-12-03 18:24 ` Neil Jerram
2010-12-03 19:45 ` Thien-Thi Nguyen
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=878w0glfuo.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).