From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] [PATCH] modulo the file size in a maildir, so it's <= 7 digits.
Date: Tue, 22 Jan 2008 20:44:47 +0000 [thread overview]
Message-ID: <1201034511-sup-3452@tomsk> (raw)
In-Reply-To: <1200970931-sup-8284@south>
On 22.1.2008, William Morgan wrote:
> God, I was hoping no one would ever see this code. And I apparently
> forgot how printf works when writing it.
:) Why do you use mtime + filesize rather than just the filename
(before the colon) as the id? Other than the flags on files (after the
colon) does this ever change?
Marcus
next prev parent reply other threads:[~2008-01-22 20:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 8:58 Jeff Balogh
2008-01-22 3:03 ` William Morgan
2008-01-22 14:01 ` Jeff Balogh
2008-01-23 5:20 ` William Morgan
2008-01-22 20:44 ` Marcus Williams [this message]
2008-01-23 5:20 ` William Morgan
2008-01-23 9:59 ` Marcus Williams
2008-01-25 5:14 ` William Morgan
2008-01-27 20:07 ` Marcus Williams
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=1201034511-sup-3452@tomsk \
--to=marcus-sup@bar-coded.net \
/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