From: Josh Huber <huber+dated+1028149268.fd896c@alum.wpi.edu>
Subject: Re: nnmaildir oddities!
Date: Fri, 26 Jul 2002 17:01:33 -0400 [thread overview]
Message-ID: <87k7nib3v6.fsf@mail.paradoxical.net> (raw)
In-Reply-To: <m31y9qkymt.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> Well, if [B t] can figure out where the article ought to go, why not
> simply pass that group instead of nil?
Exactly, this just seems to much cleaner to me...
--
Josh Huber
next prev parent reply other threads:[~2002-07-26 21:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 16:34 Josh Huber
2002-07-18 17:08 ` Paul Jarc
2002-07-18 17:57 ` Josh Huber
2002-07-18 18:21 ` Paul Jarc
2002-07-18 18:41 ` Josh Huber
2002-07-18 19:17 ` Paul Jarc
2002-07-18 20:16 ` Josh Huber
2002-07-18 20:26 ` Paul Jarc
2002-07-18 20:42 ` Josh Huber
2002-07-18 20:59 ` Paul Jarc
2002-07-18 21:27 ` Josh Huber
2002-07-18 21:32 ` Paul Jarc
2002-07-19 7:23 ` Kai Großjohann
2002-07-19 19:34 ` Josh Huber
2002-07-26 19:32 ` Simon Josefsson
2002-07-26 20:06 ` Josh Huber
2002-07-26 20:33 ` Simon Josefsson
2002-07-26 20:44 ` Paul Jarc
2002-07-26 21:01 ` Josh Huber [this message]
2002-07-26 22:40 ` Simon Josefsson
2002-07-26 21:03 ` Simon Josefsson
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=87k7nib3v6.fsf@mail.paradoxical.net \
--to=huber+dated+1028149268.fd896c@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).