From: "Andrew A. Raines" <aaraines@pobox.com>
Subject: Re: Drafts group not replacing old messages
Date: Mon, 15 Nov 2004 16:07:37 -0600 [thread overview]
Message-ID: <87vfc6epg6.fsf@mid.packer.its.vanderbilt.edu> (raw)
In-Reply-To: <87u0rqhj5r.fsf@mid.packer.its.vanderbilt.edu>
"Andrew A. Raines" <aaraines@pobox.com> writes:
[Different draft of same message.]
OK, that second one was the one I really want sent. The
first was a draft that I never actually hit send on.
After playing around 5.10.6, I'm noticing the same
behavior. I guess the draft functionality has never quite
worked right. I've never noticed a problem before,
though.
--
aaraines@pobox.com (Andrew A. Raines)
next prev parent reply other threads:[~2004-11-15 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 21:55 Andrew A. Raines
2004-11-15 22:07 ` Andrew A. Raines [this message]
2004-11-17 19:20 ` Josh
2004-11-17 20:02 ` Andrew A. Raines
2004-11-19 18:32 ` Josh
2004-11-26 20:36 ` ECB breaks Gnus (was: Drafts group not replacing old messages) Andrew A. Raines
-- strict thread matches above, loose matches on Subject: below --
2004-11-15 21:42 Drafts group not replacing old messages Andrew A. Raines
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=87vfc6epg6.fsf@mid.packer.its.vanderbilt.edu \
--to=aaraines@pobox.com \
/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).