From: Ben Rogers <brogers@columbus.rr.com>
Subject: Funny gcc behavior
Date: 28 Oct 1999 14:36:05 -0400 [thread overview]
Message-ID: <h0yacnz622.fsf@dhcp9537049.columbus.rr.com> (raw)
I've set up the "gcc-self" group parameter to make copies of most of
my sent messages to two separate groups (usually the group handling
the list and my own "sent" folder). This action exactly mimics that
of my `nnmail-split-fancy'. Or so I thought.
The problem I see is that Gcc (via `gnus-inews-do-gcc') handles these
two groups as separate archive actions, while both
`gnus-summary-respool-article' and whatever function actually stores
incoming mail (`nnmail-split-incoming'?) handles the two groups as a
single action, creating the proper `Xref' field in the message and
using only a single file linked to by both nnml directories.
Is this intended behavior? I'm guessing that `gnus-inews-do-gcc'
ought to be fixed to mimic the actions of the normal splitting
mechanism. I'd be happy to investigate a fix, but don't want to do
this if someone else has already looked into it.
ben
next reply other threads:[~1999-10-28 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-28 18:36 Ben Rogers [this message]
1999-11-07 0:10 ` 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=h0yacnz622.fsf@dhcp9537049.columbus.rr.com \
--to=brogers@columbus.rr.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).