Gnus development mailing list
 help / color / mirror / Atom feed
From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Cc: Marc Horowitz <marc@MIT.EDU>
Subject: Re: sgnus question/suggestion
Date: 04 Mar 1996 20:38:15 +0100	[thread overview]
Message-ID: <x6bumc1yrh.fsf@eyesore.no> (raw)
In-Reply-To: Marc Horowitz's message of Sun, 03 Mar 1996 15:27:21 EST

Marc Horowitz <marc@MIT.EDU> writes:

> Why is MIME handled specially in gnus-article-prepare? 

Because that's the way it was done in GNUS 4.1.  There's really no
other reason.  Since I'm waiting for Tools for Mime to be rolled into
Emacs, I saw no reason to do anything about any MIMEish things until
that happesn.

> P.S. I'm not on the list, so I'll need to be cc'd to see any
> discussion.

Put a

Mail-Copies-To: always

line in the head of the articles you send to the ding list.  Everybody
who use September to reply will then automatically Cc you.

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


      reply	other threads:[~1996-03-04 19:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-03-03 20:27 Marc Horowitz
1996-03-04 19:38 ` 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=x6bumc1yrh.fsf@eyesore.no \
    --to=larsi@ifi.uio.no \
    --cc=marc@MIT.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).