commit fd97ef8a645605929db26d56851748e03a1fa13f (patch)
parent 6edc073e doc: use separate doctrees for distinct builders
tree d1b31e642163a0ced6bfce25b0ae9289816efa56
author David Bremner <david@tethera.net> 2019-06-03 08:08:00 -0300
committer David Bremner <david@tethera.net> 2019-06-03 08:08:00 -0300
version: bump to 0.29~rc1
---
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 1583a785..f3324d28 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.29~rc0'
+__VERSION__ = '0.29~rc1'
SOVERSION = '5'
diff --git a/version b/version
index 99f09fcf..d835fcc7 100644
--- a/version
+++ b/version
@@ -1 +1 @@
-0.29~rc0
+0.29~rc1
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