From: gsstark@MIT.EDU (Greg Stark)
Subject: Selected articles, replying vs. enter-digest-group'ing
Date: 28 Feb 1996 02:57:15 -0500 [thread overview]
Message-ID: <ycqwx57vq5g.fsf_-_@fierce-bad-rabbit.MIT.EDU> (raw)
In-Reply-To: larsi@ifi.uio.no's message of 28 Feb 1996 07:59:52 +0100
It would be really cool if enter-digest-group respected the process mark.
This would involve adding features to nndoc, but would be great with those
multi-part FAQs and digests like Risks that have threads that span multiple
digests.
greg
next prev parent reply other threads:[~1996-02-28 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-27 22:12 Selected articles, replying vs. forwarding Andy Eskilsson
1996-02-28 6:59 ` Lars Magne Ingebrigtsen
1996-02-28 7:57 ` Greg Stark [this message]
1996-02-29 8:57 ` Selected articles, replying vs. enter-digest-group'ing Lars Magne Ingebrigtsen
1996-02-29 14:18 ` enter-digest-group'ing Jack Vinson
1996-02-29 17:32 ` enter-digest-group'ing Joe Hildebrand
1996-02-29 18:20 ` enter-digest-group'ing Per Abrahamsen
1996-02-28 20:11 ` Selected articles, replying vs. forwarding Edward J. Sabol
1996-02-28 20:51 ` Steve Baumgarten
1996-02-29 8:58 ` Lars Magne Ingebrigtsen
1996-02-29 8:58 ` 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=ycqwx57vq5g.fsf_-_@fierce-bad-rabbit.MIT.EDU \
--to=gsstark@mit.edu \
/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).