From: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: duplicate copies
Date: 22 Dec 1999 02:37:34 -0800 [thread overview]
Message-ID: <m3aen3clch.fsf@satellite.local.lan> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "21 Dec 1999 21:29:19 +0100"
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Harry Putnam <reader@newsguy.com> writes:
>
> > I often copy news messages to similar named nnml groups to hold for a
> > while, study, refer to or whatever. I've never managed to figure out
> > how to avoid copying duplicates to a group.
>
> I suggest a different approach, same as Brian really.
Yes, cacheing for newgroups is one way and that is what I asked
about. However in reality I copy *mail* messages to different groups
for various reasons too. And in that case the cache method is
redundant and wasteful.
I'd still like a way for gnus to let me know when I try to copy the
same message to a group where that message already resides. Or better
still:
Have gnus let me know there are dups, and ask me if I want gnus to
sort them out before `B c' ing them.
Is there already functionality that covers this or comes close?
prev parent reply other threads:[~1999-12-22 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-14 2:46 Harry Putnam
1999-12-14 3:20 ` Brian May
1999-12-21 20:29 ` Kai Großjohann
1999-12-22 10:37 ` Harry Putnam [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=m3aen3clch.fsf@satellite.local.lan \
--to=reader@newsguy.com \
--cc=ding@gnus.org \
/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).