On Tue, Nov 23, 2021 at 12:36:07PM -0800, Kevin J. McCarthy wrote:
> On Tue, Nov 23, 2021 at 08:45:47PM +0100, Hannes von Haugwitz wrote:
> > Is there any progress with this bug?
>
> Mutt 2.1.3 included the corrected sort commit referenced in my last email.
> So, for unstable/testing it would be
On Tue, Nov 23, 2021 at 08:45:47PM +0100, Hannes von Haugwitz wrote:
Is there any progress with this bug?
Mutt 2.1.3 included the corrected sort commit referenced in my last
email. So, for unstable/testing it would be nice to get 2.1.3 uploaded.
For stable/oldstable I guess it rests in the
Hello,
Is there any progress with this bug?
Best regards
Hannes
On Tue, Sep 07, 2021 at 08:20:49PM -0700, Kevin J. McCarthy wrote:
I think the probability of users encountering that in practice is low.
But if you're going through the effort of back-porting the fix, please
wait and I'll commit a corrected fix tomorrow.
This is still on a branch, waiting
Antonio,
I was going through recent Mutt commits, and I realized my fix for this
is not quite correct.
The IMAP UID field is a 32-bit unsigned integer. I unfortunately
modeled the new compare_uid() function after all the other ones use by
Mutt for sorting, which just uses subtraction.
On Wed, Aug 25, 2021 at 10:20:17AM +0200, Vincent Lefevre wrote:
> Package: mutt
> Version: 2.0.5-4.1
> Severity: grave
> Justification: causes non-serious data loss
>
> Mutt 2.1.2 is available. From the announce: "This is an important
> bug-fix release, fixing a potential data-loss IMAP bug.
Package: mutt
Version: 2.0.5-4.1
Severity: grave
Justification: causes non-serious data loss
Mutt 2.1.2 is available. From the announce: "This is an important
bug-fix release, fixing a potential data-loss IMAP bug. IMAP users
are strongly advised to upgrade."
For stable and oldstable:
7 matches
Mail list logo
