From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: nnvirtual, gcc and how to access xref header
Date: Sun, 30 Mar 2003 03:14:46 +0200 [thread overview]
Message-ID: <m3y92xac55.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <hddvfy3d6z5.fsf@bacchus.pvv.ntnu.no>
Svend Tollak Munkejord <stm@bacchus.pvv.org> writes:
> I have now read the "Posting Styles" section of the manual slightly more
> carefully, and it seems to me that the variable message-reply-headers
> refers to the message being composed, and not to the message being replied
> to.
Yes, that's right.
> Was this the "right" way of doing it?
Sure. :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-03-30 1:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 8:19 Svend Tollak Munkejord
[not found] ` <hddvfy3d6z5.fsf@bacchus.pvv.ntnu.no>
2003-03-30 1:14 ` Lars Magne Ingebrigtsen [this message]
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=m3y92xac55.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).