From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH 2/2] Use nanosecond resolution of mtime for generating the unique id for each message
Date: Fri, 19 Mar 2010 15:35:31 -0400 [thread overview]
Message-ID: <1269027265-sup-5150@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <1269026769-sup-3830@midna.zekjur.net>
Excerpts from Michael Stapelberg's message of Fri Mar 19 15:27:36 -0400 2010:
Hi Michael,
> Looks like you are right. The change won’t break on ext3, though, the
> nanoseconds will just be zero. Time to upgrade to ext4, I’d say ;-).
I like the idea here, but requiring ruby 1.9 _and_ a filesystem
upgrade for a _mail client_ is a bit of a stretch, don't you think?
Isn't there a more portable solution?
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-03-19 19:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 15:36 Michael Stapelberg
2010-03-19 19:17 ` Mark Alexander
2010-03-19 19:27 ` Michael Stapelberg
2010-03-19 19:35 ` Ben Walton [this message]
2010-03-19 19:47 ` Michael Stapelberg
2010-03-19 20:05 ` Ben Walton
2010-03-19 21:02 ` Rich Lane
2010-03-19 20:35 ` Mark Alexander
2010-03-19 21:17 ` Rich Lane
2010-03-19 19:34 ` Eric Sherman
2010-03-19 19:46 ` Michael Stapelberg
2010-03-19 20:40 ` Eric Sherman
2010-03-19 21:04 ` Mark Alexander
2010-03-20 2:23 ` Mark Alexander
2010-03-22 11:30 ` Michael Stapelberg
2010-03-22 16:25 ` Ben Walton
2010-03-25 6:25 ` Tero Tilus
2010-03-22 17:00 ` Rich Lane
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=1269027265-sup-5150@pinkfloyd.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--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