Go forward to Alternative Approaches.
Go backward to Summary Sorting.
Go up to The Summary Buffer.

Finding the Parent
==================

   If you'd like to read the parent of the current article, and it is
not displayed in the summary buffer, you might still be able to.  That
is, if the current group is fetched by NNTP, the parent hasn't expired
and the `References' in the current article are not mangled, you can
just press `^' or `A r' (`gnus-summary-refer-parent-article').  If
everything goes well, you'll get the parent.  If the parent is already
displayed in the summary buffer, point will just move to this article.

   You can have Gnus fetch all articles mentioned in the `References'
header of the article by pushing `A R'
(`gnus-summary-refer-references').

   You can also ask the NNTP server for an arbitrary article, no matter
what group it belongs to.  `M-^' (`gnus-summary-refer-article') will
ask you for a `Message-ID', which is one of those long thingies that
look something like `<38o6up$6f2@hymir.ifi.uio.no>'.  You have to get
it all exactly right.  No fuzzy searches, I'm afraid.

   If the group you are reading is located on a backend that does not
support fetching by `Message-ID' very well (like `nnspool'), you can
set `gnus-refer-article-method' to an NNTP method.  It would, perhaps,
be best if the NNTP server you consult is the same as the one that
keeps the spool you are reading from updated, but that's not really
necessary.

   Most of the mail backends support fetching by `Message-ID', but do
not do a particularly excellent job of it.  That is, `nnmbox' and
`nnbabyl' are able to locate articles from any groups, while `nnml' and
`nnfolder' are only able to locate articles that have been posted to
the current group.  (Anything else would be too time consuming.)
`nnmh' does not support this at all.