commit 4dde1e677473faa6588909396820f9948e28923f (patch)
parent 70ba2c30 set date in NEWS and debian/changelog
tree 1f477fcf0fe8f9b218fb7b3d9b0ea5008bb1b522
author David Bremner <david@tethera.net> 2016-12-24 17:52:11 +0900
committer David Bremner <david@tethera.net> 2016-12-24 17:52:11 +0900
version: update to 0.23.4
---
bindings/python/notmuch/version.py | 2 +-
version | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/bindings/python/notmuch/version.py b/bindings/python/notmuch/version.py
index 98ea31b5..b5d308e2 100644
--- a/bindings/python/notmuch/version.py
+++ b/bindings/python/notmuch/version.py
@@ -1,3 +1,3 @@
# this file should be kept in sync with ../../../version
-__VERSION__ = '0.23.3'
+__VERSION__ = '0.23.4'
SOVERSION = '4'
diff --git a/version b/version
index 9e40e75c..40a6dfed 100644
--- a/version
+++ b/version
@@ -1 +1 @@
-0.23.3
+0.23.4
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