Gnus development mailing list
 help / color / mirror / Atom feed
From: "Arne Jørgensen" <arne@arnested.dk>
Subject: Re: A new Gnus 5.10 release...
Date: Mon, 20 Mar 2006 23:58:00 +0100	[thread overview]
Message-ID: <arne4q1s7mh3.fsf@arnested.dk> (raw)
In-Reply-To: <v9y7z5nd3x.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> AFAICS, the following changes could be merged from the trunk into the
> stable branch.  The question is just whether to do it before or
> shortly after the release.  Does anyone have pending fixes that need
> go into v5-10?.

I have mostly looked at S/MIME-stuff (although not very much during
the last couple of months).

The only bug I know about in 5.10.x (and in No Gnus) is that
`gnus-message-replysignencrypted' has no effect replying on encrypted
S/MIME-messages. But I don't think it's ever been reported by anyone.

When I looked at several months ago I didn't find any easy way to
solve it.

So I would say go for it anyway!

Kind regards,
-- 
Arne Jørgensen <http://arnested.dk/>




  parent reply	other threads:[~2006-03-20 22:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 19:13 Reiner Steib
2006-03-20 19:22 ` gdt
2006-03-20 20:24 ` Romain Francoise
2006-03-20 22:58 ` Arne Jørgensen [this message]
2006-03-21  5:22 ` Manoj Srivastava
2006-03-21 15:44   ` Romain Francoise
2006-03-21 14:51 ` Simon Josefsson
2006-03-21 17:14   ` Reiner Steib
2006-03-22  9:55     ` Simon Josefsson
2006-03-22 15:01       ` Reiner Steib
2006-03-22 16:06         ` Simon Josefsson
2006-03-22  6:14 ` Katsumi Yamaoka
2006-03-23  9:47   ` Katsumi Yamaoka
2006-03-23 12:35     ` Reiner Steib
2006-03-23 14:25       ` Katsumi Yamaoka
2006-04-04 15:08 ` Release candidate for 5.10.8 (was: A new Gnus 5.10 release...) Reiner Steib
2006-04-07 15:44   ` Release candidate for 5.10.8 Reiner Steib
2006-04-08  9:10     ` Reiner Steib

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=arne4q1s7mh3.fsf@arnested.dk \
    --to=arne@arnested.dk \
    /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).