Re: [PATCH] Re: Bad charset conversion with gpg-signed mime-forward.

To: Mutt Developers <mutt-dev@xxxxxxxx>
Subject: Re: [PATCH] Re: Bad charset conversion with gpg-signed mime-forward.
From: Laurent Fousse <laurent@xxxxxxxxxx>
Date: Sat, 19 Feb 2005 15:54:36 +0100
In-reply-to: <20050219135045.GF6645@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-unsubscribe: <mailto:mutt-dev-request@mutt.org?body=unsubscribe>
Mail-followup-to: Mutt Developers <mutt-dev@xxxxxxxx>
References: <20050218172323.GA13521@xxxxxxxxxxxxxxxxxxxxxx> <20050219065806.GD14345@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20050219123334.GA3902@xxxxxxxxxxxxxxxxxxxxxx> <20050219135045.GF6645@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-mutt-dev@xxxxxxxx
User-agent: Mutt/1.5.6+20040907i

* Thomas Roessler [2005-02-19]:
> > I don't know how this affects forwarded messages.
> 
> Could you try this patch and report if it fixes the problem for you?

Yes, it fixes the problem. Thanks a lot!

Attachment: signature.asc
Description: Digital signature

Follow-Ups:
- Re: [PATCH] Re: Bad charset conversion with gpg-signed mime-forward.
  - From: Tamotsu Takahashi

References:
- Bad charset conversion with gpg-signed mime-forward.
  - From: Laurent Fousse
- Re: Bad charset conversion with gpg-signed mime-forward.
  - From: Tamotsu Takahashi
- Re: Bad charset conversion with gpg-signed mime-forward.
  - From: Laurent Fousse
- [PATCH] Re: Bad charset conversion with gpg-signed mime-forward.
  - From: Thomas Roessler

Prev by Date: [PATCH] Re: Bad charset conversion with gpg-signed mime-forward.
Next by Date: Re: For 1.5.9 - (problem w/ pgp_autoinline)
Previous by thread: [PATCH] Re: Bad charset conversion with gpg-signed mime-forward.
Next by thread: Re: [PATCH] Re: Bad charset conversion with gpg-signed mime-forward.
Index(es):
- Date
- Thread