Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: mail-header-separator starting with whitespace fails
Date: Thu, 29 Jan 2015 11:31:26 +0900	[thread overview]
Message-ID: <b4mbnlil3lt.fsf@jpl.org> (raw)
In-Reply-To: <87bnlinyrx.fsf@building.gnus.org>

On Thu, 29 Jan 2015 12:47:30 +1100, Lars Ingebrigtsen wrote:
> I've now made message.el remove the separator when using smtpmail, too.
> That should probably fix the problem the user had.

> Should perhaps be backported to emacs-24 if this doesn't lead to any
> problems.

Thanks.  That shouldn't cause any problem, I believe.  So, I've
merged it to both the trunk and the emacs-24 branch.



      reply	other threads:[~2015-01-29  2:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 16:31 Russ Allbery
2014-05-14  0:41 ` Katsumi Yamaoka
2014-05-16 23:35   ` Russ Allbery
2015-01-28  5:49   ` Lars Ingebrigtsen
2015-01-28  8:33     ` Katsumi Yamaoka
2015-01-29  1:47       ` Lars Ingebrigtsen
2015-01-29  2:31         ` Katsumi Yamaoka [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=b4mbnlil3lt.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --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).