From: Andreas Schwab <schwab@redhat.com>
To: overseers@sourceware.org
Subject: Spurious CRs in bugzilla mails
Date: Thu, 24 Mar 2011 09:13:00 -0000 [thread overview]
Message-ID: <m3pqpgswxp.fsf@redhat.com> (raw)
Since around 2011-03-23 14:00 all bugzilla mails contain spurious CRs at
the end of the body lines. Coincidentally, at the same time the mail
are apparently no longer spam filtered (the X-SWARE-Spam-Status and
X-Spam-Check-By headers are absent). Those extra CRs get turned into
NLs when injected into gmane, which is kinda annoying.
Andreas.
--
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
next reply other threads:[~2011-03-24 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 9:13 Andreas Schwab [this message]
2011-03-24 11:38 ` Frank Ch. Eigler
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=m3pqpgswxp.fsf@redhat.com \
--to=schwab@redhat.com \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).