🚀 go-pugleaf

In article <1992Oct28.181209.6099@netcom.com> strnlght@netcom.com (David Sternlight) writes:

>Though the bug has been fixed in trn, Pete Holsberg asks "how is a thread
>determined?"
>
>In the listing of messages, each thread has an access letter, then
>a series of topics and messages for that thread. Usually there is
>one topic, but sometimes (with the old bug) more than one for a
>particular access letter.

Sorry, but thank you for playing.  That is how trn diagrams the
various threads and discussion trees to the reader, not how threads
are organized at their basic level; it is a consequence, not a cause,
of message threading.

Trn determines which messages fall into particular threads by
judicious organization of the References and Message-ID headers of
individual articles.  Each article posted to Usenet has a unique
Message-ID implanted in its header lines.  Followups to that article
add a References header with the Message-ID of the parent article
appended to it; further followups take the parent's References header,
add its Message-ID, and use the result for their own References
header.  Each time an article arrives at your site, the trn package
studies its References header to determine if it belongs in any
existing threads, and files it away within that thread if that's the
case.

There are certain exceptions; for example, if an article has no
References header but has a subject line identical to an existing
thread, it gets grouped in with the other articles in that thread, but
you can't immediately tell which article spawned it as a response.

-- 
____ Tim Pierce                / "You are just naive and repressed because
\  / twpierce@unix.amherst.edu /  penis envy is here and it's now and it's
 \/ (BITnet: TWPIERCE@AMHERST) /  all around you." -- Neal C. Wickham