commit af51e67127e5817e3795973da9c5e2148b7fdeec (patch)
parent cda6e4d1 version: update to 0.30~rc2
tree 100d78992d1e4ea5b8cb5dad42dd6fb8e4cdb885
author David Bremner <david@tethera.net> 2020-06-16 08:32:51 -0300
committer David Bremner <david@tethera.net> 2020-06-16 08:42:07 -0300
debian: changelog stanza for 0.30~rc2-1
---
debian/changelog | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index 704b54f6..a858b5db 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+notmuch (0.30~rc2-1) experimental; urgency=medium
+
+ * New upstream release candidate.
+ * Upstream fixes for new python bindings (python3-notmuch2).
+ * Update debian/copyright (one new author).
+
+ -- David Bremner <bremner@debian.org> Tue, 16 Jun 2020 08:32:16 -0300
+
notmuch (0.30~rc1-1) experimental; urgency=medium
* New upstream release candidate
glossary
--------
Commit objects reference one tree, and zero or more parents.
Single parent commits can typically generate a patch in
unified diff format via `git format-patch'.
Multiple parents means the commit is a merge.
Root commits have no ancestor. Note that it is
possible to have multiple root commits when merging independent histories.
Every commit references one top-level tree object.
git clone https://yhetil.org/notmuch.git