From: "William M. Perry" <wmperry@aventail.com>
Cc: ding@gnus.org
Subject: Re: Incorrect behaviour with MML and Gcc:?
Date: Wed, 26 May 1999 06:26:25 -0500 [thread overview]
Message-ID: <374BDA61.CB6EA3D2@aventail.com> (raw)
In-Reply-To: <m3ogj8zwdt.fsf@deneb.cygnus.stuttgart.netsurf.de>
Yes, but when you say 'hmmmm... I know I sent that sample code to
so-and-so last month' and go to look for it in your archives, you are
screwed. :)
-bp
Florian Weimer wrote:
> Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
>
> > Right now, MML does not get expanded when doing Gcc. This is a bug.
>
> Oh, and I considered it a feature. I do like that attachments are no
> longer stored in my outgoing mail archive automatically. ;)
prev parent reply other threads:[~1999-05-26 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-25 14:23 Nathan Williams
1999-05-25 16:28 ` Kai.Grossjohann
1999-05-25 16:50 ` Hrvoje Niksic
1999-05-25 17:09 ` David S. Goldberg
1999-05-25 17:36 ` Kai.Grossjohann
1999-05-25 21:12 ` Florian Weimer
1999-05-26 11:26 ` William M. Perry [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=374BDA61.CB6EA3D2@aventail.com \
--to=wmperry@aventail.com \
--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).