Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: ell 0.38 bluez 5.56
Date: Sun, 11 Apr 2021 06:13:19 +0200	[thread overview]
Message-ID: <20210411041319.SvMeDfXvYkT9LLN5xZ4MxQOwcDuYeHPfeRnK8tSN6d0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28488@inbox.vuxu.org>

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

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

ell 0.38 bluez 5.56
https://github.com/void-linux/void-packages/pull/28488

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-04-11  4:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04 18:24 [PR PATCH] ell: update to 0.37 ericonr
2021-02-04 18:29 ` [PR PATCH] [Updated] " ericonr
2021-02-04 18:49 ` [NOMERGE] nell: " ericonr
2021-02-04 18:58 ` ericonr
2021-02-05  2:00 ` [NOMERGE] ell: " sgn
2021-02-05  2:06 ` ericonr
2021-02-05  2:06 ` ericonr
2021-02-05  2:06 ` ericonr
2021-02-05  2:07 ` ericonr
2021-02-05  2:07 ` ericonr
2021-02-05  2:11 ` sgn
2021-02-05  2:13 ` sgn
2021-02-26 20:23 ` [PR PATCH] [Updated] " ericonr
2021-02-27  0:15 ` iwd 1.12 ell 0.38 bluez 5.56 sgn
2021-03-01 15:07 ` sgn
2021-03-01 15:09 ` sgn
2021-03-01 18:25 ` ericonr
2021-03-11 20:48 ` [PR PATCH] [Updated] " ericonr
2021-03-11 20:49 ` ericonr
2021-04-07 14:00 ` paper42
2021-04-07 14:15 ` paper42
2021-04-07 15:46 ` [PR PATCH] [Updated] " ericonr
2021-04-07 15:47 ` ericonr
2021-04-07 15:47 ` [PR PATCH] [Updated] " ericonr
2021-04-07 17:48 ` paper42
2021-04-10 11:01 ` paper42
2021-04-11  4:13 ` ericonr [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=20210411041319.SvMeDfXvYkT9LLN5xZ4MxQOwcDuYeHPfeRnK8tSN6d0@z \
    --to=ericonr@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).