What's needed for mutt 1.6?
- To: Mutt Developers <mutt-dev@xxxxxxxx>
- Subject: What's needed for mutt 1.6?
- From: Brendan Cully <brendan@xxxxxxxxxx>
- Date: Thu, 22 Feb 2007 09:30:33 -0800
- Dkim-signature: a=rsa-sha1; c=relaxed; d=kublai.com; h=received:received:date:to:subject:message-id:mime-version:content-type:content-disposition:x-operating-system:user-agent:from:mail-followup-to:x-delivery-agent; q=dns; s=dk; bh=XHqx+MBcinSiuP5ynPJ1LsuZPB4=; b=PMJnG9Q2mAgUt9896yMV/cAZTxPE5Kqhx0AWzgMXKpszqn8/UeEd1NAyl7akABzgtrYz+q8WLONDp742g+xS0dkbVIp/k2u5LszrGNYfq57hcVdENHPw+WvE8bwzoxj1M/cnfKjrp8yfI8/8xlNK537u6W6hzd0QzAQoh0l6KIU=
- List-unsubscribe: <mailto:email@example.com?Subject="Unsubscribe Mutt Dev"?body=unsubscribe>
- Mail-followup-to: mutt-dev@xxxxxxxx
- Sender: owner-mutt-dev@xxxxxxxx
- User-agent: Mutt/1.5.13 (2007-02-12)
I intend to cut 1.5.14 this weekend. I'd like to make 1.5.15 the last
proper dev release for 1.6 - that is, feature-freeze after
1.5.15. So, I'd like to hear once again which patches everyone would
like to see in 1.6 (and which patches people object to).
On my list at the moment:
I'll probably apply my ESMTP patch (*dons flame suit*)
And I think the configurable umask patch is handy.
assumed-charset might be a good idea too.
I do not intend to visit the great config-var rename topic until after
1.6 by the way. I think it would need too much time to deal with the
Description: PGP signature