From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: mu4e: update to 1.10.3
Date: Thu, 27 Apr 2023 21:16:51 +0200 [thread overview]
Message-ID: <20230427191651.X5oBH3aCotoEFSOuaYmYM2EOutr65JJz2FNADrtb2EI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43116@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
There's a merged pull request on the void-packages repository
mu4e: update to 1.10.3
https://github.com/void-linux/void-packages/pull/43116
Description:
#### Testing the changes
- I tested the changes in this PR: **Yes**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x86_64-musl (crossbuild)
- aarch64 (crossbuild)
- armv7l (crossbuild)
#### Notes
- changed build style to `meson` as it is the primary build option of `mu`
- removed `guile` build option because it depends on `guile-3.x`.
- users will have to re-initialize their database (`mu-init(1)`)
prev parent reply other threads:[~2023-04-27 19:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 14:18 [PR PATCH] mu4e: update to 1.10.0 pascal-huber
2023-04-01 10:31 ` [PR PATCH] [Updated] " pascal-huber
2023-04-03 11:03 ` pascal-huber
2023-04-03 11:04 ` mu4e: update to 1.10.1 pascal-huber
2023-04-03 11:05 ` pascal-huber
2023-04-05 16:21 ` [PR PATCH] [Updated] " pascal-huber
2023-04-11 8:48 ` pascal-huber
2023-04-11 8:48 ` mu4e: update to 1.10.2 pascal-huber
2023-04-15 23:05 ` [PR PATCH] [Updated] " pascal-huber
2023-04-15 23:05 ` mu4e: update to 1.10.3 pascal-huber
2023-04-26 19:15 ` [PR PATCH] [Updated] " pascal-huber
2023-04-27 19:16 ` Duncaen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230427191651.X5oBH3aCotoEFSOuaYmYM2EOutr65JJz2FNADrtb2EI@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).