From: Karl Kleinpaste <karl@jprc.com>
Subject: auto-expiration should take effect in crossposted copies, yes?
Date: 10 Jan 1997 11:23:40 -0500 [thread overview]
Message-ID: <vxkloa1v6r7.fsf@pocari-sweat.jprc.com> (raw)
I have (auto-expire) in most of my mailing lists. I also catch copies
of anything I write in nnml:personal.karl, where auto-expiration is
not in effect. If I send something to ding@ifi.uio.no, when it comes
back from the list, it will be crossposted to both personal.karl and
list.ding. Fine so far.
The problem I see, though, is that reading my own post in
personal.karl first will cause it not to be marked `E'xpirable in
list.ding, as everything there should be. It is merely marked `O'
there.
Is it not appropriate that crossposts to auto-expirable groups be
noticed, and marked as such?
next reply other threads:[~1997-01-10 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-10 16:23 Karl Kleinpaste [this message]
1997-01-14 23:29 ` 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=vxkloa1v6r7.fsf@pocari-sweat.jprc.com \
--to=karl@jprc.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).