From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: ding@ifi.uio.no
Subject: Re: Decoding QP stuff...
Date: 16 Feb 1997 14:31:17 +0100 [thread overview]
Message-ID: <rjbu9kubbu.fsf@zuse.dina.kvl.dk> (raw)
In-Reply-To: visigoth@naiad.fac.cs.cmu.edu's message of 16 Feb 1997 07:27:41 -0500
visigoth@naiad.fac.cs.cmu.edu writes:
> Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
>
> > That would horribly break threading.
>
> Oh, well. The ability to have one article be a member of two threads
> is theoretically elegant, but as with most such things, won't be
> happening Any Time Soon.
Gnus could use See-Also: for the remaining articles.
Defined in Son-of-RFC 1036.
next prev parent reply other threads:[~1997-02-16 13:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-13 22:24 visigoth
1997-02-14 8:53 ` Kai Grossjohann
1997-02-15 8:49 ` visigoth
1997-02-16 8:28 ` Lars Magne Ingebrigtsen
1997-02-16 12:27 ` visigoth
1997-02-16 13:31 ` Per Abrahamsen [this message]
1997-02-16 22:10 ` Lars Magne Ingebrigtsen
1997-02-14 9:42 ` Lars Magne Ingebrigtsen
[not found] <Pine.WNT.3.95.970214075040.168A-100000@kirk.nca.asu.edu>
1997-02-15 8:53 ` visigoth
1997-02-16 3:07 ` Mark Eichin
1997-02-16 15:39 ` Kai Grossjohann
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=rjbu9kubbu.fsf@zuse.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
--cc=ding@ifi.uio.no \
/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).