From: Marshall T. Vandegrift <vandem2@rpi.edu>
Subject: Proposal for `gnus-gcc-inhibit-security'
Date: Sat, 19 Apr 2003 11:15:20 -0400 [thread overview]
Message-ID: <87vfxaecxj.fsf@rpi.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
Hi,
In gnu.emacs.gnus there was a discussion that resulted in the
following message:
<news://news.gmane.org/iluu1cuk5xw.fsf@latte.josefsson.org>
and Simon Josefsson suggesting the possibility of a
`gnus-gcc-inhibit-security' variable that would suppress the
processing of `#secure' MML directives when posting via GCC.
What do people think? I like the idea, and would like to see it
implemented. In fact, I'm willing to try implementing it myself, but
I'm new here ;-) and just starting to find my way around the Gnus
code. So if this does seem like a good idea and no one else wants to
do it, I'll start writing...
--
Marshall T. Vandegrift <vandem2@rpi.edu>
They were all, one might say, nonexistent, but each
non-existed in an entirely different way.
-- Stanislaw Lem, /The Cyberiad/
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2003-04-19 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 15:15 Marshall T. Vandegrift [this message]
2003-04-19 15:30 ` Marshall T. Vandegrift
2003-04-27 3:18 ` Lars Magne Ingebrigtsen
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=87vfxaecxj.fsf@rpi.edu \
--to=vandem2@rpi.edu \
/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).