From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: maildir without hardlinks?
Date: Tue, 03 Sep 2002 16:52:15 -0400 [thread overview]
Message-ID: <874rd6zthc.fsf@mail.paradoxical.net> (raw)
In-Reply-To: <m3ofbesvz5.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> I think the easiest change would be to make the .../read/* entries
> be links to one file, and the .../expire/* entries be links to
> another file. Then everything works the same as before, with just a
> few extra inodes per group. I'll put this on my todo list.
Cool, this is what I had in mine as well.
Thanks,
--
Josh Huber
prev parent reply other threads:[~2002-09-03 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 18:48 Josh Huber
2002-09-03 19:39 ` Paul Jarc
2002-09-03 20:52 ` Josh Huber [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=874rd6zthc.fsf@mail.paradoxical.net \
--to=huber@alum.wpi.edu \
--cc=huber+dated+1031518323.6c39f9@alum.wpi.edu \
/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;
as well as URLs for NNTP newsgroup(s).