commit fd20a31e4cf2485d0446a844f9facf54592728ba (patch)
parent cf68a0c2 NEWS: start entry for 0.27
tree 0449d2f28fd45903302c746c0ea04168bf3b3859
author David Bremner <david@tethera.net> 2018-05-27 13:15:48 -0700
committer David Bremner <david@tethera.net> 2018-05-27 13:15:48 -0700
debian: update symbols for 0.27
add two new API symbols
---
debian/libnotmuch5.symbols | 2 ++
1 file changed, 2 insertions(+)
diff --git a/debian/libnotmuch5.symbols b/debian/libnotmuch5.symbols
index 5e408213..308567b8 100644
--- a/debian/libnotmuch5.symbols
+++ b/debian/libnotmuch5.symbols
@@ -47,8 +47,10 @@ libnotmuch.so.5 libnotmuch5 #MINVER#
notmuch_message_add_property@Base 0.23~rc0
notmuch_message_add_tag@Base 0.3
notmuch_message_count_files@Base 0.26~rc0
+ notmuch_message_count_properties@Base 0.27~rc0
notmuch_message_destroy@Base 0.3
notmuch_message_freeze@Base 0.3
+ notmuch_message_get_database@Base 0.27~rc0
notmuch_message_get_date@Base 0.3
notmuch_message_get_filename@Base 0.3
notmuch_message_get_filenames@Base 0.5
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