informing the users of the new behavior of write_bcc

[software/mutt-debian.git] / debian / NEWS

diff --git a/debian/NEWS b/debian/NEWS
index 0e9aad5d9e83bdb8b07eb88ba59e3b7291897f24..2ea8a59e66d9ea19befb6705c1345f042aebcd99 100644 (file)
--- a/debian/NEWS
+++ b/debian/NEWS
@@ -1,3 +1,28 @@
+mutt (1.5.20-6) unstable; urgency=low
+  The behavior of the write_bcc option has changed, now write_bcc is only
+  used to decide if an Fcc message should have its Bcc header written;
+  if the message is sent outside using SMTP the Bcc header will never be
+  written, see the description of debian-specific/467432-write_bcc.patch
+  for details
+
+ -- Antonio Radici <antonio@dyne.org>  Tue, 19 Jan 2010 21:57:48 +0000
+
+mutt (1.5.17-2) unstable; urgency=low
+
+  There is now a "mutt-patched" package that will contain some more
+  experimental patches. For now that is the "sidebar" patch. See
+  README.Patches for details.
+
+ -- Christoph Berg <myon@debian.org>  Tue, 01 Jan 2008 20:03:16 +0100
+
+mutt (1.5.16-2) unstable; urgency=low
+
+  User-visible changes in this version:
+  * The gpgme crypt backend is not yet stable enough, disabled again.
+  * The imap_home_namespace variable was removed upstream.
+
+ -- Christoph Berg <myon@debian.org>  Thu, 28 Jun 2007 20:58:49 +0200
+
 mutt (1.5.14+cvs20070301-1) experimental; urgency=low
 
   We no longer unset write_bcc in /etc/Muttrc. If your MTA does not strip Bcc: