NEWS.org: update

NEWS.org

@@ -9,19 +9,28 @@
  (1.13 -> 1.14) until incompatible changes are required; for now working in the
  1.12 series seems a good way to get improvements to users more quickly.
 
-  - man documentation improvements
+  - many bug fixes
 
-  - message composition has been reworked to avoid a number of problems user
+  - many documentation improvements
-    reported. It is now directly uses the Gnus machinery, but integrate inside
+
-    mu4e.
+  - you can now search for messages that have a given message-id in their
+    ~References:~ or ~In-Reply-To:~ headers, e.g.
+    #+begin_example
+    mu find ref:0D9218A9-C7F5-4D50-B49C-FCE201114C9B@gmail.com
+    #+end_example
+    You do need to re-index the database for this to work though.
+
+  - message composition has been completely reworked to avoid a number of
+    problems user reported. It is now directly uses the Gnus machinery, but
+    integrate inside mu4e.
 
   - with 1.12.7, ~mu~ indexing is single-threaded again, to avoid cases of
-    database-corruption.
+    database-corruption. In *mu4e* that means you need to _wait_ until indexing is
+    ready before you can continue (*mu4e* will warn you).
 
-    This, unfortunately, means that in *mu4e* you need to _wait_ until indexing is
+    If you see that warning often, perhaps your indexing is too slow; see the
-    ready before you can continue (*mu4e* will warn you). If you see that warning
+    section on "Speeding up indexing" in [[info:mu4e#Retrieval and indexing][Retrieval and indexing]] in the mu4e
-    often, perhaps your indexing is too slow, see the section on "Speeding up
+    manual.
-    indexing" in [[info:mu4e#Retrieval and indexing][Retrieval and indexing]] in the mu4e manual.
 
     Note: for a while, the single-threadedness was signified by an "-st" suffix
     in the mu4e version in its main-page; however, since this is optional no