From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: Michael Stapelberg <michael+sup@stapelberg.de>
Cc: kevinr@mit.edu, sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Return nothing between if end index is not found.
Date: Thu, 09 Sep 2010 12:55:25 -0400 [thread overview]
Message-ID: <1284051078-sup-224@ezyang> (raw)
In-Reply-To: <1282085130-sup-6401@midna.zekjur.net>
Excerpts from Michael Stapelberg's message of Tue Aug 17 18:46:32 -0400 2010:
> Interesting. I gzipped it (to make sure it does not get touched in any way on
> its way to you) and attached it to this mail.
I finally got around to looking at your message, and as expected, it appears
that there is no trailing END PGP MESSAGE block, which is why my patch breaks
your behavior (it claims there is no valid PGP block.)
Regardless of what the PGP standard says, I suppose it's good practice
to be liberal in what we accept. So the correct change might be to
keep the existing semantics of between (documenting carefully what happens
if the ending line is not present) and then fixing the code that relies
on the bogus invariant.
This also resolves Kevin Riggle’s issue.
Cheers,
Edward
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-09-09 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-18 17:53 Edward Z. Yang
2010-07-19 22:50 ` Michael Stapelberg
2010-07-20 20:09 ` Michael Stapelberg
2010-08-15 23:30 ` Edward Z. Yang
2010-08-16 1:19 ` Michael Stapelberg
2010-08-16 1:40 ` Edward Z. Yang
2010-08-16 16:27 ` Alvaro Herrera
2010-08-16 17:22 ` Michael Stapelberg
2010-08-16 19:55 ` Edward Z. Yang
2010-08-17 22:46 ` Michael Stapelberg
2010-09-09 16:55 ` Edward Z. Yang [this message]
2010-09-09 19:08 ` Kevin Riggle
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1284051078-sup-224@ezyang \
--to=ezyang@mit.edu \
--cc=kevinr@mit.edu \
--cc=michael+sup@stapelberg.de \
--cc=sup-devel@rubyforge.org \
/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