From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: overseers@sourceware.cygnus.com
Subject: RE2: Re: Why have the prior 2 "gcc Digest" emails *not* been digests?(fwd)
Date: Tue, 30 May 2000 13:03:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.21.0005302202140.93459-100000@deneb.dbai.tuwien.ac.at> (raw)
Message-ID: <20000530130300.3mU9x_pFf2SZ5zYZyIQaQB2QLvKPaTUVXKFcylpJkFk@z> (raw)
A few days ago I forwarded another message by David, which Jason and/or
Jeff were so kind to have a look at; perhaps the following provides the
crucial hint?
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
---------- Forwarded message ----------
From: David Presberg <David.Presberg@conexant.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: David.Presberg@conexant.com, gcc-help@gcc.gnu.org
Date: Tue, 30 May 2000 11:59:58 -0400 (EDT)
Subject: RE2: Re: Why have the prior 2 "gcc Digest" emails *not* been
digests?
Gerald --
Hmmm. Note the following (?) randomness:
D gcc-digest-help@gcc.gnu.o 24May 08:29 941/31837
"gcc Digest 24 May 2000 08:29:36 -0000 Issue 674"
T gcc-owner@gcc.gnu.org 25May 12:03 1469/52200
"gcc Digest 25 May 2000 12:03:47 -0000 Issue 675"
T gcc-owner@gcc.gnu.org 26May 10:52 1269/45209
"gcc Digest 26 May 2000 10:52:18 -0000 Issue 676"
T gcc-owner@gcc.gnu.org 27May 18:12 1193/40599
"gcc Digest 27 May 2000 18:12:10 -0000 Issue 677"
D gcc-digest-help@gcc.gnu.o 28May 14:16 1126/35666
"gcc Digest 28 May 2000 14:16:49 -0000 Issue 678"
D gcc-digest-help@gcc.gnu.o 29May 15:20 1056/36941
"gcc Digest 29 May 2000 15:20:23 -0000 Issue 679"
T* gcc-owner@gcc.gnu.org 30May 15:30 1450/55179
"gcc Digest 30 May 2000 15:30:32 -0000 Issue 680"
where:
"D" == (proper digest). "T" == "Content-Type: text/plain; charset=us-ascii".
but:
"T*" == "Content-Type: multipart/mixed;
Boundary="0__=882568EF005567FF8f9e8a93df938690918c882568EF005567FF".
which latter is still not a proper digest-form email.
And only the proper digests have the extra header-lines that explain
about getting off the list, etc.
[...]
next reply other threads:[~2000-05-30 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Gerald Pfeifer [this message]
2000-05-30 13:03 ` Gerald Pfeifer
2000-12-30 6:08 ` RE2: Re: Why have the prior 2 "gcc Digest" emails *not* been digests? (fwd) Jason Molenda
2000-05-31 13:52 ` Jason Molenda
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=Pine.BSF.4.21.0005302202140.93459-100000@deneb.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=overseers@sourceware.cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).