Linux bluetooth development
 help / color / mirror / Atom feed
From: Sebastian Reichel <sre@kernel.org>
To: Travis Griggs <travisgriggs@gmail.com>
Cc: Bluez mailing list <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez5.44 and Debian?
Date: Sat, 6 May 2017 03:26:34 +0200	[thread overview]
Message-ID: <20170506012634.vtnewlnj6nexpliq@earth> (raw)
In-Reply-To: <DB5F6CBF-43D4-492C-8542-346887D7C881@gmail.com>

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

Hi,

On Fri, May 05, 2017 at 04:25:51PM -0700, Travis Griggs wrote:
> Does anyone know why bluez 5.44 (which was pushed in February) is
> still not available in debian-unstable? I thought unstable was
> usually pretty current.

Debian is currently preparing the stretch release, so Debian
maintainers avoid uploading new packages to unstable except
for fixing release-critical bugs.

-- Sebastian

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-05-06  1:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 23:25 bluez5.44 and Debian? Travis Griggs
2017-05-06  1:26 ` Sebastian Reichel [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=20170506012634.vtnewlnj6nexpliq@earth \
    --to=sre@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=travisgriggs@gmail.com \
    /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