2 new changesets in mutt:
http://dev.mutt.org/hg/mutt/rev/53e5e1105fd2
changeset: 5165:53e5e1105fd2
branch: HEAD
tag: tip
user:Thomas Roessler <[EMAIL PROTECTED]>
date:Sat Jun 09 01:03:09 2007 +0200
summary: remove unnecessary dprints
http://dev.mutt.org/hg/mutt
On 2007-06-08 15:09:51 +, Rocco Rutte wrote:
> A dirty fix was to change 'break' in that function to 'continue', but now
> the subject header for your example gets quite long (2 lines compared to
> 3)... but I don't know if that's what header wrapping was all about.
So... This was a combin
On 2007-06-08 15:09:51 +, Rocco Rutte wrote:
> Mutt is supposed to continue on line 2 since it's actually within
> an encoded word (but it doesn't know since it never saw '=?'). So
> the first part evaluates to false since the word is "too long"
> and in_encoded_word errorneously is 0.
Actual
On Sat, 09 Jun 2007 the mental interface of
Brendan Cully told:
> 2 new changesets in mutt:
>
> http://dev.mutt.org/hg/mutt/rev/53e5e1105fd2
> changeset: 5165:53e5e1105fd2
> branch: HEAD
> tag: tip
> user:Thomas Roessler <[EMAIL PROTECTED]>
> date:Sat Jun 09 01:03:0
On Saturday, 09 June 2007 at 19:15, Elimar Riesebieter wrote:
> On Sat, 09 Jun 2007 the mental interface of
> Brendan Cully told:
>
> > 2 new changesets in mutt:
> >
> > http://dev.mutt.org/hg/mutt/rev/53e5e1105fd2
> > changeset: 5165:53e5e1105fd2
> > branch: HEAD
> > tag: tip
> >
#2901: wrong parameter micalg with mutt 1.5.15 and gpgme
Changes (by brendan):
* status: reopened => closed
* resolution: => fixed
Comment:
(In [e6f958b093b6]) Make GPGME backend generate a RFC3156-compliant micalg
parameter
(blush). Based on a patch by Stefan Haun. Closes #2901.
--
It's that time again. This release is largely a bug-fix release, but
it does contain a couple of small new features (next-unread-mailbox,
$message_cache_clean). Looking at the number of bugs marked as
blockers for 1.6*, I think we're not quite ready to announce release
candidates yet. But the devel
* Brendan Cully on Saturday, June 09, 2007 at 21:03:59 -0700:
> It's that time again.
Heh. Great.
> This release is largely a bug-fix release, but it does contain
> a couple of small new features (next-unread-mailbox,
> $message_cache_clean).
But $message_cache_clean is not doing anything yet, i
