From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: references on multiple message followup
Date: Tue, 19 Feb 2002 20:27:27 -0500 [thread overview]
Message-ID: <vxkeljhvt6o.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <87lmdpj92f.fsf@zip.com.au> (Kevin Ryde's message of "Wed, 20 Feb 2002 10:22:48 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> If I process mark a couple of articles to followup, so as to quote all
> the text, the references constructed seems to be based only on the
> first article.
> I wonder if the references from all the articles could be included.
> Or if that's a bit hard then maybe use the last article instead of the
> first.
The problem is that References is, in principle, a strict linear
parentage list from head to tail of a thread. Trying to use
References with multiple, immediately-referring message-ids creates
something of a lattice, abandoning the linear interpretation.
Reputedly, the USEFOR draft includes a much-modified concept of
In-Reply-To which can contain the message-ids of all messages to which
the new message refers. (I confess to not having personally seen
USEFOR's draft in an indecently long time.) But I don't believe
there's any support for that yet.
In any event, complicating matters is the problem of how one would
thread a message in a summary display, based on linear References
interpretation, that had lattice-like References content.
next prev parent reply other threads:[~2002-02-20 1:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 0:22 Kevin Ryde
2002-02-20 1:27 ` Karl Kleinpaste [this message]
2002-02-22 0:26 ` Kevin Ryde
2002-02-22 0:26 ` Kevin Ryde
2002-02-20 1:27 ` Karl Kleinpaste
2002-02-20 6:04 ` Wes Hardaker
2002-02-20 6:04 ` Wes Hardaker
2002-02-20 0:22 Kevin Ryde
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=vxkeljhvt6o.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.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).