From: Jason Molenda <jason-swarelist@molenda.com>
To: overseers@sources.redhat.com
Cc: Jonathan Larmour <jlarmour@redhat.com>, overseers@sourceware.cygnus.com
Subject: Re: [Fwd: failure notice]
Date: Wed, 30 Aug 2000 13:15:00 -0000 [thread overview]
Message-ID: <20000830131422.A26689@shell17.ba.best.com> (raw)
Message-ID: <20000830131500.iJ10-IJIBqYIh7MFBIwclbuuTmaVFy9Q3Guhtua0vXI@z> (raw)
In-Reply-To: <20000830153622.B27245@cygnus.com>
On Wed, Aug 30, 2000 at 03:36:22PM -0400, Chris Faylor wrote:
> I looked at the script and I can see why it does fail on two Cc: lines.
> I don't see any obvious way to fix this. Are two Cc: lines even legal in
> a header? Especially when the first line ends with a comma?
I don't know if it's legal, but it got delivered. If it were me,
I'd probably say "Don't do that" - this is the first report I've
ever seen of someone sending out a msg like that. But if Jonathan
thinks it's important enough, he can always dig in to it himself.
To fix it, I'd probably add some code to count the number of To: and Cc:
lines in the headers, and then loop over them somehow.
J
next prev parent reply other threads:[~2000-08-30 13:15 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Jonathan Larmour
2000-08-30 11:12 ` Jonathan Larmour
2000-12-30 6:08 ` Jason Molenda
2000-08-30 11:32 ` Jason Molenda
2000-12-30 6:08 ` Jason Molenda
2000-08-30 12:03 ` Jason Molenda
2000-12-30 6:08 ` Chris Faylor
2000-08-30 12:37 ` Chris Faylor
2000-12-30 6:08 ` Jason Molenda [this message]
2000-08-30 13:15 ` Jason Molenda
2000-12-30 6:08 ` Chris Faylor
2000-08-30 13:45 ` Chris Faylor
2000-12-30 6:08 ` Jonathan Larmour
2000-08-30 13:51 ` Jonathan Larmour
2000-12-30 6:08 ` Chris Faylor
2000-08-30 14:01 ` Chris Faylor
2000-12-30 6:08 ` Jonathan Larmour
2000-08-30 14:13 ` Jonathan Larmour
2000-12-30 6:08 Stan Shebs
2000-07-07 8:56 ` Stan Shebs
2000-12-30 6:08 ` Jim Kingdon
2000-07-07 9:43 ` Jim Kingdon
2000-12-30 6:08 ` Chris Faylor
2000-07-07 15:30 ` Chris Faylor
2000-12-30 6:08 ` Jim Kingdon
2000-07-07 18:46 ` Jim Kingdon
2000-12-30 6:08 ` Chris Faylor
2000-07-07 19:05 ` Chris Faylor
2001-04-23 11:46 Jonathan Larmour
2001-04-23 11:50 ` Jonathan Larmour
2002-03-05 12:18 Joel Sherrill
2002-03-07 20:57 ` Andrew Cagney
2002-08-16 20:19 Ulrich Drepper
2002-08-16 20:25 ` Christopher Faylor
2003-02-01 2:32 Robert Love
2003-02-01 2:53 ` Christopher Faylor
2003-06-04 4:30 Joern Rennecke
[not found] <1066412429.25550.133.camel@doubledemon.codesourcery.com>
2003-10-17 17:58 ` root
2003-11-17 15:23 Andrew Cagney
2003-11-18 7:48 ` law
2003-11-18 14:40 ` Andrew Cagney
2003-11-18 15:53 ` Matthew Galgoci
2003-11-18 16:18 ` Ian Lance Taylor
2003-11-18 16:28 ` Christopher Faylor
2003-11-18 16:16 ` Christopher Faylor
2003-11-18 16:23 ` Andrew Cagney
2003-11-18 16:33 ` Christopher Faylor
2003-11-18 16:16 ` Ian Lance Taylor
2004-08-18 17:20 Corinna Vinschen
2004-08-18 17:44 ` Ian Lance Taylor
2004-08-18 17:54 ` Corinna Vinschen
2004-08-18 18:52 ` Ian Lance Taylor
2004-08-18 22:13 ` Ian Lance Taylor
2004-08-18 22:21 ` Corinna Vinschen
2007-02-19 21:12 Mark Mitchell
2007-02-19 21:21 ` Christopher Faylor
2007-02-19 22:03 ` Mark Mitchell
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=20000830131422.A26689@shell17.ba.best.com \
--to=jason-swarelist@molenda.com \
--cc=jlarmour@redhat.com \
--cc=overseers@sources.redhat.com \
--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).