From: Norman Walsh <norm@berkshire.net>
Subject: B m creates duplicates?
Date: 17 May 1997 12:27:05 -0400 [thread overview]
Message-ID: <uvi4idpye.fsf@berkshire.net> (raw)
Hello world,
I've just started using "B m" to move mail between groups
(mostly so I can have even greater refinement than I can
practically create with procmail) and I notice that articles
moved this way are flagged as duplicates.
Since I'm moving them, not copying them or otherwise duplicating
them, I think this is a bug. It's not a serious one, since I
can just go through and tick them as unread, but...FYI...
--norm
next reply other threads:[~1997-05-17 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-17 16:27 Norman Walsh [this message]
1997-05-19 0:30 ` Lars Magne Ingebrigtsen
1997-05-19 12:51 ` David S. Goldberg
1997-05-19 15:16 ` Norman Walsh
1997-05-19 18:55 ` Norman Walsh
1997-05-20 20:20 ` Lars Magne Ingebrigtsen
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=uvi4idpye.fsf@berkshire.net \
--to=norm@berkshire.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;
as well as URLs for NNTP newsgroup(s).