commit 2a0b123ea603535d31c867c61cfd3d1908db3e7c (patch)
parent b8ccfe34 version: bump to 0.25~rc1
tree 353305393c167ed2ddf8d0aa103e2832aa4e41f3
author David Bremner <david@tethera.net> 2017-07-18 07:06:04 -0300
committer David Bremner <david@tethera.net> 2017-07-18 07:12:12 -0300
debian: finalize changelog for 0.25~rc1-1
---
debian/changelog | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index a0224176..cab4b9cf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,9 @@
-notmuch (0.25~rc0-3) UNRELEASED; urgency=medium
+notmuch (0.25~rc1-1) experimental; urgency=medium
* Bump standards version to 4.0.0 (no changes needed)
+ * New upstream release candidate
- -- David Bremner <bremner@debian.org> Tue, 18 Jul 2017 06:41:21 -0300
+ -- David Bremner <bremner@debian.org> Tue, 18 Jul 2017 07:04:14 -0300
notmuch (0.25~rc0-2) experimental; urgency=medium
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