aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
...
* | Merge tag 'debian/0.17-2'Gravatar David Bremner2014-01-01
|\| | | | | | | uploaded to unstable
| * debian: rename NEWS.Debian to NEWSGravatar David Bremner2014-01-01
| | | | | | | | | | Apparently I had it backwards: NEWS is installed as NEWS.Debian, not vice-versa.
* | Merge tag '0.17'Gravatar David Bremner2013-12-30
|\| | | | | | | notmuch 0.17 release
| * devel/release-checks.sh: adjust to LIBNOTMUCH version checksGravatar Tomi Ollila2013-12-30
| | | | | | | | | | | | NOTMUCH_VERSION_* macros in lib/notmuch.h are replaced with LIBNOTMUCH_VERSION_* macros. Check that the values of those match the LIBNOTMUCH_*_VERSION values in lib/Makefile.local.
| * version: bump to 0.17Gravatar David Bremner2013-12-30
| |
| * debian: add changelog and NEWS.Debian for releaseGravatar David Bremner2013-12-30
| | | | | | | | | | NEWS.Debian is displayed at install, so we include the news item about the disruptive change in sha1 computation.
| * debian: disable atomicity tests on ia64Gravatar David Bremner2013-12-30
| | | | | | | | | | | | | | | | | | | | The following fails on Debian ia64: % gdb /bin/mv (gdb) break rename Since this breaks our atomicity test, disable them until someone is motivated to figure out whose fault that is.
* | Merge tag '0.17_rc4'Gravatar David Bremner2013-12-28
|\| | | | | | | notmuch 0.17~rc4 release
| * version: bump to 0.17~rc4Gravatar David Bremner2013-12-28
| | | | | | | | | | Unfortunately release-checks.sh will whine a bit because it has not caught up with the renaming of the version macros.
| * test: Fix transient error in 'new' testGravatar Austin Clements2013-12-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes a non-deterministic failure in "Ignore files and directories specified in new.ignore (multiple occurrences)". The test assumed that all directories would be scanned, even though nothing updated the mtime of ${MAIL_DIR}. It *usually* worked nevertheless because the tests run quickly enough that the directory mtime is usually the same as the current time, so notmuch new does not update the mtime in the database (because more changes could occur in the same second). However, when it occasionally did update the mtime in the database, the notmuch new call in this test would (correctly) skip "pass 2" of scanning ${MAIL_DIR}, causing it to skip the following expected lines: (D) add_files_recursive, pass 2: explicitly ignoring ${MAIL_DIR}/.git (D) add_files_recursive, pass 2: explicitly ignoring ${MAIL_DIR}/.ignored_hidden_file (D) add_files_recursive, pass 2: explicitly ignoring ${MAIL_DIR}/ignored_file This patch fixes this problem by touching ${MAIL_DIR} to ensure it gets scanned and by rearranging the test to ensure the directories are touched immediately before the main notmuch new call in the test.
| * test: remove call to notmuch-hello from emacs_deliver_messageGravatar David Bremner2013-12-22
| | | | | | | | | | | | | | There is an obscure bug in notmuch-hello that very occasionally causes emacs_deliver_message to fail. Since it it doesn't serve any actual purpose in the function we delete it, and leave tracking down the the bug for another day.
| * test: add emacs_fcc_message that does not use smtp-dummyGravatar David Bremner2013-12-22
| | | | | | | | | | | | | | Most of the tests previously using emacs_deliver_message do not use the actual transmitted message, so we replace it with a simpler (and presumably more reliable function) that only saves (and indexes) an fcc copy of the message.
* | perf-test: bump version to 0.4, use manifest filesGravatar David Bremner2013-12-10
| | | | | | | | | | The new revision of the performance test includes manifests for each corpus, so update the support library to use these manifests at the same time.
* | emacs: add '?' to some prefix keymaps to describe its bindingsGravatar Mark Walters2013-12-10
| | | | | | | | | | Added function notmuch-subkeymap-help to describe keybindings of a subkeymap (eg after . or c in notmuch-search and notmuch-show).
* | test: implement and document NOTMUCH_TEST_QUIET variable usageGravatar Tomi Ollila2013-12-09
| | | | | | | | | | | | When NOTMUCH_TEST_QUIET environment variable is set to non-null value messages when new test script starts and when test PASSes are disabled. This eases picking the cases when tests FAIL (as those are still printed).
* | test: print empty line at the beginning of test script, not at endGravatar Tomi Ollila2013-12-09
| | | | | | | | | | | | In preparation for quiet mode print empty line before writing the test description. This is done now in function designed for it -- it will also be called when test fails.
* | test: resolve `basename "$0" .sh` once for all in test-lib.shGravatar Tomi Ollila2013-12-09
| | | | | | | | | | | | | | | | | | | | test-lib.sh sometimes did equivalent of `basename "$0" .sh`, sometimes skipping the basename part and sometimes .sh part. This worked as we never had path components in $0 (more than ./) nor .sh ending. Now the equivalent of `basename "$0" .sh` is done once and used everywhere. In the future we may have .sh suffix in test names -- removing those is a good idea.
| * test: give unique timestamps to messagesGravatar David Bremner2013-12-09
| | | | | | | | | | | | The choice of decreasing timestamps is a hack which reduces the number of existing tests which fail. This can be changed to increasing if/when somebody wants update another 47 tests.
| * test: sanitize dates in emacs, raw, and text outputGravatar David Bremner2013-12-09
| | | | | | | | | | | | | | add a new function notmuch_date_sanitize for rfc822-ish things. Add date sanitization to notmuch_show_sanitize_all and use it more places. This is all in aid of a transition to unique timestamps on messages.
| * test: sanitize Date and timestamp fields in jsonGravatar David Bremner2013-12-09
| | | | | | | | | | | | | | | | | | Eventually we want test messages to have distinct dates to avoid reproducability problems. This sanitization will prevent some test failures when that change is made. Replace the use of a local function in maildir-sync with notmuch_json_show_sanitize
| * test: pass expected output through json_sanitize in 2 placesGravatar David Bremner2013-12-09
|/ | | | | This makes the tests more robust against changes in the sanitization rules.
* version: bump versionGravatar David Bremner2013-12-07
| | | | | | | | Roll (one last?) release candidate because of Austin's LIBNOTMUCH_VERSION changes. Atomically bump the manually (NEWS, debian/changelog) and automatically (everywhere else) updated places version is mentioned.
* lib: Bump library version from 3.0.0 to 3.1.0Gravatar Austin Clements2013-12-07
| | | | | | This version of the library introduces LIBNOTMUCH_CHECK_VERSION and the *_VERSION macros. Bumping the version number is also necessary to make the comment on LIBNOTMUCH_CHECK_VERSION no longer a lie.
* lib: Replace NOTMUCH_*_VERSION with LIBNOTMUCH_*_VERSIONGravatar Austin Clements2013-12-07
| | | | | | This makes it clear that these macros refer to the *library* version, and not to the notmuch application-level release. Since there are no consumers of these macros yet, this is now or never.
* lib: Make VERSION macros agree with soname versionGravatar Austin Clements2013-12-07
| | | | | | | | | | | | | | | | | | We have two distinct "library version" numbers: the soname version and the version macros. We need both for different reasons: the version macros enable easy compile-time version detection (and conditional compilation), while the soname version enables runtime version detection (which includes the version checking done by things like the Python bindings). However, currently, these two version numbers are different, which is unnecessary and can lead to confusion (especially in things like Debian, which include the soname version in the package name). This patch makes them the same by bumping the version macros up to agree with the soname version. (We should probably keep the version number in just one place so they can't get out of sync, but that can be done in another patch.)
* News updates for Mark's bugfixesGravatar Mark Walters2013-12-01
|
* debian: reformat changelog to avoid lintian warning.Gravatar David Bremner2013-11-30
|
* NEWS: bump dateGravatar David Bremner2013-11-28
|
* version: bump to 0.17~rc2Gravatar David Bremner2013-11-28
|
* debian: update changelog for new release candidateGravatar David Bremner2013-11-28
|
* test/crypto: disable gpg version printingGravatar David Bremner2013-11-28
| | | | | | This was causing test failures because version strings varied in length between GNU/Linux and GNU/KFreeBSD. One can also imagine different versions of gnupg causing the same failure.
* vim: NEWS for vim interfaceGravatar David Bremner2013-11-28
| | | | Transcribed from Felipe's email.
* debian: remove warning about emacs24Gravatar David Bremner2013-11-27
|
* util: detect byte orderGravatar David Bremner2013-11-27
| | | | | | | | Unfortunately old versions of GCC and clang do not provide byte order macros, so we re-invent them. If UTIL_BYTE_ORDER is not defined or defined to 0, we fall back to macros supported by recent versions of GCC and clang
* NEWS: News for big endian sha1 bug fix.Gravatar David Bremner2013-11-25
| | | | | We could give more details about how to migrate tags, but I'm not sure that it's a practical problem, or just a theoretical one.
* lib: fix byte order test in libsha1.cGravatar David Bremner2013-11-25
| | | | | | | | | | Previously PLATFORM_BYTE_ORDER and IS_LITTLE_ENDIAN were not defined, so the little endian code was always compiled in. This will have the effect that the "SHA1s" on big endian architectures will change (i.e. become actual sha1s). So someone re-indexing their database could conceivable lose tags on messages without a message-id header.
* debian: disable gdb as a build-dependency on s390xGravatar David Bremner2013-11-24
| | | | | | Gdb is currently broken on s390x buildd's and porterboxes (see #728705). By removing it as a build-dep, we disable the (failing) atomicity test on this architecture
* Add NEWS entry for notmuch-compactGravatar Ben Gamari2013-11-24
| | | | Signed-off-by: Ben Gamari <bgamari.foss@gmail.com>
* debian: add notmuch_database_compact to symbols file.Gravatar David Bremner2013-11-23
| | | | This change does not require an SONAME bump because it only adds a symbol.
* debian: changelog stanza for release candidateGravatar David Bremner2013-11-23
|
* version: bump to 0.17~rc1Gravatar David Bremner2013-11-23
| | | | | Various other files are synched using "make update-versions". NEWS has to be hand edited.
* NEWS: remove blank line.Gravatar David Bremner2013-11-23
| | | | Tomi says I have to.
* test: replace $PWD with YYY in emacs & emacs-show testsGravatar David Bremner2013-11-23
| | | | | | | | | | | | | | When executed command line is written to *Notmuch errors* buffer, shell-quote-argument will backslash-escape any char that is not in "POSIX filename characters" (i.e. matching "[^-0-9a-zA-Z_./\n]"). Currently in two emacs tests shell has expanded $PWD as part of emacs variable, which will later be fed to #'shell-quote-argument and finally written to ERROR file. If $PWD contained non-POSIX filename characters, data in ERROR file will not match $PWD when later comparing in shell. Therefore, in these two particular cases the escaped $PWD is replaced with YYY in ERROR file and expected content is adjusted accordingly.
* emacs: show: stop stderr appearing in bufferGravatar Mark Walters2013-11-20
| | | | | | | | | | | | | | | | | | | | | | In emacs 24.3+ the stdout/stderr from externally displaying an attachment gets inserted into the show buffer. This is caused by changes in mm-display-external in mm-decode.el. Ideally, we would put this output in the notmuch errors buffer but the handler is called asynchronously so we don't know when the output will appear. Thus if we put it straight into the errors buffer it could get interleaved with other errors. Also we can't easily tell when we have got all the error output so can't wait until the process is complete. One solution would be to create a new buffer for the stderr of each attachment viewed. Again, since we can't tell when the process has finished, we can't close these buffers automatically so this will leave lots of buffers around. Thus we add a debug variable notmuch-show-attachment-debug: it this is non-nil we create a new buffer for each viewer; if this variable is nil we just use a temp buffer which means all error output is discarded (this is the same behaviour as with emacs pre 24.3).
* vim: add help fileGravatar Felipe Contreras2013-11-20
| | | | Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
* vim: check compose is done on deleteGravatar Felipe Contreras2013-11-20
| | | | | | Not on unload, which happens when we switch buffers. Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
* vim: remove unnecessary buffer queueGravatar Felipe Contreras2013-11-20
| | | | | | | Vim handles the buffers just fine: when one is deleted, we go to the previous one. Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
* vim: add wrapper for old variable namesGravatar Felipe Contreras2013-11-20
| | | | Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
* vim: move default sets to set_defaults()Gravatar Felipe Contreras2013-11-20
| | | | Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
* vim: rename public notmuch_rb variablesGravatar Felipe Contreras2013-11-20
| | | | Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-03 13:40:12 +0000