From: "Sébastien Villemot" <sebastien.villemot@ens.fr>
To: Daiki Ueno <ueno@unixuser.org>
Cc: 9862@debbugs.gnu.org
Subject: bug#9862: 23.3; [Gnus/EasyPG] Mixing PGP/MIME signature with RFC822 forwarded multipart message results in an invalid MIME message
Date: Wed, 26 Oct 2011 11:13:05 +0200 [thread overview]
Message-ID: <877h3sru8u.fsf@karaba.cepremap.org> (raw)
In-Reply-To: <m3lis9a3ki.fsf-ueno@unixuser.org> (Daiki Ueno's message of "Tue, 25 Oct 2011 17:16:45 +0900")
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
Daiki Ueno <ueno@unixuser.org> writes:
> Could you try newer Gnus from the git?
I am going to compile from the git and tell you if the problem is fixed
there for me.
If it is, then it would be great if you could provide a patch for the
23.x series, so that we can fix the bug in Debian (I don't know when
24.x is expected to be released).
Thanks for your work,
--
Sébastien Villemot
Researcher in Economics at CEPREMAP & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-49-90 - GPG Key: 4096R/381A7594
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-10-26 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 20:36 bug#9862: 23.3; [Gnus/EasyPG] Mixing PGP/MIME signature with RFC822 forwarded multipart message results in an invalid MIME message S=e9bastien Villemot
2011-10-24 22:07 ` bug#9862: Additional information Sébastien Villemot
2011-10-25 8:16 ` bug#9862: 23.3; [Gnus/EasyPG] Mixing PGP/MIME signature with RFC822 forwarded multipart message results in an invalid MIME message Daiki Ueno
2011-10-25 17:01 ` Andreas Schwab
2011-10-26 1:59 ` Daiki Ueno
2011-10-26 9:13 ` Sébastien Villemot [this message]
2011-10-26 10:09 ` Sébastien Villemot
2011-10-26 19:43 ` Andreas Schwab
2011-11-05 20:21 ` Sébastien Villemot
2011-11-07 6:15 ` Daiki Ueno
2011-10-25 9:49 ` bug#9862: Stéphane Adjemian
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=877h3sru8u.fsf@karaba.cepremap.org \
--to=sebastien.villemot@ens.fr \
--cc=9862@debbugs.gnu.org \
--cc=ueno@unixuser.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.