commit d0469c5b4c6ed9188b96b12363fced45291813fd (patch)
parent 522b279e debian: start changelog for 0.38.3-1
tree 20a21be526079adc466c51f93c29c3de6b812acf
author David Bremner <david@tethera.net> 2024-03-09 22:51:06 -0400
committer David Bremner <david@tethera.net> 2024-03-09 22:51:31 -0400
version: bump to 0.38.3
---
bindings/python/notmuch/version.py | 2 +-
version.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/bindings/python/notmuch/version.py b/bindings/python/notmuch/version.py
index f4fd171d..fd4152ee 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.38.2'
+__VERSION__ = '0.38.3'
SOVERSION = '5'
diff --git a/version.txt b/version.txt
index f2e78d49..f2687f32 100644
--- a/version.txt
+++ b/version.txt
@@ -1 +1 @@
-0.38.2
+0.38.3
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