From: Neil Jerram <neil@ossau.uklinux.net>
To: Mike Gran <spk121@yahoo.com>
Cc: Ken Raeburn <raeburn@raeburn.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: fencepost error in encoding processing
Date: Sun, 15 Nov 2009 22:46:35 +0000 [thread overview]
Message-ID: <87zl6nfltg.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <184417.3577.qm@web37907.mail.mud.yahoo.com> (Mike Gran's message of "Sun, 15 Nov 2009 00:48:57 -0800 (PST)")
Mike Gran <spk121@yahoo.com> writes:
>> Okay to check in?
>
> FWIW, it looks right to me.
Yes, it looks good to me too. My only comment is that it took me a
while to see what you meant by 'fencepost'. I'm not familiar with
that expression, and thought it was something to do with building on
fencepost.gnu.org. So you might like to add some further explanation to
the commit message when you commit.
Regards,
Neil
next prev parent reply other threads:[~2009-11-15 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 4:36 fencepost error in encoding processing Ken Raeburn
2009-11-15 8:48 ` Mike Gran
2009-11-15 22:46 ` Neil Jerram [this message]
2009-11-16 7:32 ` Mike Gran
2009-11-16 22:03 ` Richard E. Harke
2009-11-16 13:03 ` Ludovic Courtès
2009-11-16 17:25 ` Ken Raeburn
2009-11-16 21:51 ` Ludovic Courtès
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=87zl6nfltg.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=raeburn@raeburn.org \
--cc=spk121@yahoo.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).