Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: mu: update to 1.6.3 & combine mu and mu4e packages
Date: Sat, 14 Aug 2021 15:23:26 +0200	[thread overview]
Message-ID: <20210814132326.FY1-92OZ2qQ_jn6tqzmiYvOLmUMjkcZkEzxEYMFWc9Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32396@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]

There's a merged pull request on the void-packages repository

mu: update to 1.6.3 & combine mu and mu4e packages
https://github.com/void-linux/void-packages/pull/32396

Description:
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [X] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


      parent reply	other threads:[~2021-08-14 13:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-07 16:18 [PR PATCH] mu: update to 1.6.2 emacsomancer
2021-08-08  3:52 ` sgn
2021-08-08 12:47 ` emacsomancer
2021-08-08 12:48 ` emacsomancer
2021-08-08 13:18 ` sgn
2021-08-08 13:42 ` emacsomancer
2021-08-08 16:03 ` sgn
2021-08-08 16:34 ` emacsomancer
2021-08-08 16:34 ` emacsomancer
2021-08-08 16:36 ` emacsomancer
2021-08-08 17:25 ` [PR PATCH] [Updated] " emacsomancer
2021-08-12  0:47 ` emacsomancer
2021-08-12 21:22 ` emacsomancer
2021-08-12 21:26 ` emacsomancer
2021-08-12 21:31 ` [PR PATCH] [Updated] " emacsomancer
2021-08-12 21:58 ` emacsomancer
2021-08-12 22:02 ` emacsomancer
2021-08-12 22:03 ` emacsomancer
2021-08-13  0:48 ` [PR PATCH] [Updated] mu: update to 1.6.3 & combine mu and mu4e packages emacsomancer
2021-08-13  2:07 ` [PR REVIEW] " sgn
2021-08-13  2:07 ` sgn
2021-08-13  2:29 ` [PR PATCH] [Updated] " emacsomancer
2021-08-13  2:30 ` [PR REVIEW] " emacsomancer
2021-08-13  2:30 ` emacsomancer
2021-08-14 13:23 ` sgn [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=20210814132326.FY1-92OZ2qQ_jn6tqzmiYvOLmUMjkcZkEzxEYMFWc9Q@z \
    --to=sgn@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).