* David Bremner:
> Yes, there was a brief discussion [...]
Thanks. As I expected, it was my lack of attention that led to me being
caught unawares. ;-)
> I guess xz compression is something packagers will have to deal with.
Of course, no worries. I am not miffed in any way, especially because i
Ralph Seichter writes:
> * David Bremner:
>
>> https://notmuchmail.org/releases/notmuch-0.29.tar.xz
>
> As the maintainer of Notmuch in MacPorts, I wonder why you chose to
> switch from a classical tarball to a .tar.xz archive? Did I miss some
> discussion on this mailing list?
Yes, there was a
* David Bremner:
> https://notmuchmail.org/releases/notmuch-0.29.tar.xz
As the maintainer of Notmuch in MacPorts, I wonder why you chose to
switch from a classical tarball to a .tar.xz archive? Did I miss some
discussion on this mailing list?
-Ralph
__
William Casarin writes:
> I couldn't run the performance tests on my machines due to a hardcoded
> bash path. Use env for finding bash in weird systems like NixOS.
>
> Signed-off-by: William Casarin
pushed to master
d
___
notmuch mailing list
notmuch
I'm pondering running uncrustify on all/most of the notmuch codebase,
but I noticed a few things that uncrustify does are either not
documented in STYLE, or maybe contradicted.
1) Should block comments start with '*' ? Uncrustify thinks yes, STYLE
is silent, the codebase says mostly yes. I th
Where to obtain notmuch 0.29
===
https://notmuchmail.org/releases/notmuch-0.29.tar.xz
Which can be verified with:
https://notmuchmail.org/releases/notmuch-0.29.tar.xz.sha256.asc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
08e926aba53c4b0337fe7907d4f44e76ecc5eaa5d
