From: prj@po.cwru.edu (Paul Jarc)
Cc: ding@gnus.org
Subject: Re: Adding headers to supersedes buffers
Date: Mon, 25 Mar 2002 19:10:53 -0500 [thread overview]
Message-ID: <m3bsdcyyqk.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <3226089779771480@oakhurst.yi.org> (Thomas Skogestad's message of "Tue, 26 Mar 2002 01:02:59 +0100")
Thomas Skogestad <tskogest@jusstud.uio.no> wrote:
> I'd prefer that supersedes buffers inherit the posting style
> settings for the group I'm superseding in.
They do, for me. How do you set your posting style? How do you
create the superseding message buffer?
paul
next prev parent reply other threads:[~2002-03-26 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3225897212316912@oakhurst.yi.org>
2002-03-25 22:46 ` Paul Jarc
[not found] ` <3226087887457301@oakhurst.yi.org>
2002-03-25 23:36 ` Paul Jarc
[not found] ` <3226089779771480@oakhurst.yi.org>
2002-03-26 0:10 ` Paul Jarc [this message]
[not found] ` <3226121299894383@oakhurst.yi.org>
2002-03-26 17:23 ` Paul Jarc
[not found] ` <3226155549108258@oakhurst.yi.org>
2002-03-26 18:31 ` Paul Jarc
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=m3bsdcyyqk.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=ding@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).