From: Mike Kelly <pioto@pioto.org>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] mbox date fail
Date: Sun, 1 Nov 2009 18:30:07 -0500 [thread overview]
Message-ID: <20091101183007.0b90de33@aether.home.pioto.org> (raw)
In-Reply-To: <1257101109-sup-4117@masanjin.net>
On Sun, 01 Nov 2009 10:46:33 -0800
William Morgan <wmorgan-sup@masanjin.net> wrote:
> Yep, that's what I've done. I couldn't get my local system to throw
> ArgumentError, even with your example, but if it's possible, it's
> possible, and should be caught.
Yep, that seems to help. Thanks! (I altered the example slightly for
anonymity reasons, that might have invalidated it as a test case).
--
Mike Kelly
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-11-01 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 21:13 Mike Kelly
2009-11-01 18:46 ` William Morgan
2009-11-01 23:30 ` Mike Kelly [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091101183007.0b90de33@aether.home.pioto.org \
--to=pioto@pioto.org \
--cc=sup-talk@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