From: Bud Rogers <budr@tanet.net>
Cc: ding@gnus.org
Subject: Re: broken-reply-to
Date: 22 Jan 1998 07:25:55 -0600 [thread overview]
Message-ID: <m2k9bsmyho.fsf@twocups.tanet.net> (raw)
In-Reply-To: Justin Sheehy's message of "21 Jan 1998 23:34:29 -0500"
Justin Sheehy <justin@linus.mitre.org> writes:
> The Group Parameters is a list of lists.
>
> So, the complete entry would be:
>
> ((broken-reply-to . t))
Yeah, a couple of friendly souls already clued me into that. Thanks.
--
Bud Rogers <budr@tanet.net>
prev parent reply other threads:[~1998-01-22 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-21 21:33 broken-reply-to Bud Rogers
1998-01-22 0:58 ` broken-reply-to Mark Moll
1998-01-22 4:34 ` broken-reply-to Justin Sheehy
1998-01-22 13:25 ` Bud Rogers [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=m2k9bsmyho.fsf@twocups.tanet.net \
--to=budr@tanet.net \
--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).