Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: Edward Z. Yang <ezyang@mit.edu>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Return nothing between if end index is not found.
Date: Wed, 18 Aug 2010 00:46:32 +0200	[thread overview]
Message-ID: <1282085130-sup-6401@midna.zekjur.net> (raw)
In-Reply-To: <1281979589-sup-7759@ezyang>

[-- Attachment #1: Type: text/plain, Size: 367 bytes --]

Hi Edward,

Excerpts from Edward Z. Yang's message of 2010-08-16 21:55:32 +0200:
> Fascinatingly enough, I cannot find it in either my inbox or my spam filter. (Dun dun dun.)
> Maybe you should send it as an attachment.
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.

Best regards,
Michael

[-- Attachment #2: fwd.gz --]
[-- Type: application/x-gzip, Size: 3130 bytes --]

[-- Attachment #3: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

  reply	other threads:[~2010-08-17 22:46 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 [this message]
2010-09-09 16:55                 ` Edward Z. Yang
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=1282085130-sup-6401@midna.zekjur.net \
    --to=michael+sup@stapelberg.de \
    --cc=ezyang@mit.edu \
    --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