| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
Since I already pushed a tag 0.13_rc-1, let's just increment the
debian version to keep everything tidy.
|
|
|
|
|
| |
This symbol is apparently part of the exclude code that was disabled
for 0.12.
|
|
|
|
|
|
|
|
| |
we need
- a new changelog stanza, because the symbols files need a new version
- s/libnotmuch2/libnotmuch3/ everywhere
- update symbols file, s/.so.1/.so.2/, and bump minimum versions on changed
symbols (although the latter is just documentation)
|
|
|
|
|
| |
This is mainly so that the soname bump in the debian symbols file
makes sense.
|
|
|
|
|
| |
gnupg-agent is required for message decryption, so this should help
stem some issues encountered by users trying to decrypt messages.
|
| |
|
| |
|
|
|
|
| |
Include extremely terse summary of NEWS.
|
|
|
|
| |
mention the two bugfixes
|
|
|
|
| |
As explained in f34613e, if using gmime 2.6, we want at least 2.6.7
|
|
|
|
| |
No actual changes are needed.
|
|
|
|
| |
Ignore individual binary package directories.
|
|
|
|
|
| |
This symbol is added in 0.12, although we are "stealthing" the feature
overall.
|
| |
|
|
|
|
|
|
| |
libgmime-2.6-dev entered debian unstable today. If 2.6 is available,
notmuch should build against 2.6 instead of 2.4, as 2.6 is the current
upstream stable version of libgmime.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
NEWS
bindings/python/notmuch/database.py
bindings/python/notmuch/message.py
notmuch.1
NEWS merged by hand, others taken from master.
|
| |
| |
| |
| | |
mention the two bugfixes
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
notmuch-reply.c
notmuch.1
|
| | |
|
| |
| |
| |
| | |
as usual for pre-releases, fairly minimal commentary.
|
| |
| |
| |
| | |
Set dist=experimental the first time.
|
| |
| |
| |
| | |
Previous version was actually uploaded to experimental, not unstable
|
| |
| |
| |
| |
| | |
We now have man pages in sections 5 and 7 as well, so we copy the
whole /usr/share/man hierarchy.
|
|/
|
|
| |
and keep python, man page, and debian package in sync.
|
|
|
|
| |
Debian tags have been using '/', instead of '-' as a separator.
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
NEWS
Conflicts resolved by inserting the 0.10.2 stanza before 0.11
|
| | |
|
| | |
|
|\| |
|
| | |
|
|/
|
|
|
|
| |
Since version 0.8 of dtach -n does no longer require controlling
tty to be present when executed. Currently controlling tty is not
always (if ever) present when tests are executed.
|
|
|
|
| |
Give a brief summary of (and pointer to) NEWS
|
|
|
|
|
| |
Arguably editing debian/changelog violates the "do one thing at a
time" rule, but all of these versions need to be kept in sync.
|
|
|
|
| |
Since this is only an added symbol, no soname bump required.
|
|
|
|
|
| |
The changelog is a bit minimalist, but we'll do better for the real
release.
|
|
|
|
|
| |
This reflects a modification to the test suite to use dtach instead of
screen.
|
|
|
|
|
| |
No functional change, but this will make for cleaner diffs down the
line.
|
|
|
|
| |
This is needed for emacs tests, now that those are run in screen.
|
|
|
|
|
| |
Admit that there have been no changes since the last release
candidate.
|
|
|
|
| |
Document upstream changes since 0.9~rc1-1
|
|
|
|
|
|
|
|
| |
we need
- a new changelog stanza, because the symbols files need a new version
- s/libnotmuch1/libnotmuch2/ everywhere
- update symbols file, s/.so.1/.so.2/, and bump minimum versions on changed
symbols (although the latter is just documentation)
|
| |
|
|
|
|
| |
This is needed to enable the atomicity tests at build time.
|
|
|
|
|
| |
The bug was really closed by the commit that updated the dependency,
of course.
|
|
|
|
|
|
| |
As long as we have no version information in the json output, this
seems like the only possible way of ensuring that the emacs client
code understands the output from the command line tool notmuch.
|
| |
|
|
|
|
|
| |
There are three new symbols in libnotmuch. In addition to notmuch_{begin,end)_atomic,
notmuch_database_find_message_by_filename was exposed.
|
| |
|
|
|
|
| |
See commit 6979b65 for more discussion.
|
|
|
|
|
|
|
|
|
|
| |
we now have three files to keep in sync. That seems wrong, but I guess
we will live with it for now.
The main problem is that the python code is distributed separately, so
it can't get the version from 'version'.
The choice ~rcX is for convenience with debian versioning.
|