From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: 39692@debbugs.gnu.org
Subject: [bug#39692] [PATCH] gnu: bluez: Update to 5.53.
Date: Thu, 20 Feb 2020 16:21:29 +0100 [thread overview]
Message-ID: <87pne9xp1i.fsf@nckx> (raw)
In-Reply-To: <20200220145853.14697-1-brice@waegenei.re>
[-- Attachment #1: Type: text/plain, Size: 301 bytes --]
Brice Waegeneire 写道：
> * gnu/packages/linux.scm (bluez): Update to 5.53.
Looks good assuming you've rebuilt all dependents (‘guix refresh
-l’).
Because of the high number of dependents, this patch wil have to
be applied to the next ‘core-updates’ branch.
Thanks!
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-02-20 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 14:58 [bug#39692] [PATCH] gnu: bluez: Update to 5.53 Brice Waegeneire
2020-02-20 15:21 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-02-24 18:56 ` bug#39692: " Marius Bakke
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pne9xp1i.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=39692@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).