New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 708257 link

Starred by 3 users
Status: Verified
Owner:
█ mcchou@chromium.org
Last visit > 30 days ago
Closed: Apr 2017
Cc:
josephsih@chromium.org
snanda@chromium.org
r...@chromium.org
█ bhthompson@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 708291
issue 704196



Sign in to add a comment

Create a new branch in bluez repo based on BlueZ 5.44 release

Project Member Reported by mcchou@chromium.org, Apr 4 2017 
A new branch is needed for updating BlueZ to 5.44. The new branch should be created based on the Linux BlueZ upstream 5.44 release, and Chromium-specific patches will be applied on top of the new branch.

repo:
    chromiumos/third_party/bluez

branching source:
    BlueZ upstream (git://git.kernel.org/pub/scm/bluetooth/bluez.git)

name of the new branch:
    chromeos-5.44

starting git sha1:
commit 54d05d4c66ab6512bae5ce47b1537dea3237b8d1
Author: Marcel Holtmann <marcel@holtmann.org>
Date:   Sat Feb 25 17:02:37 2017 +0100

    Release 5.44

Comment 1 by mcchou@chromium.org, Apr 4 2017

Cc: -chromeos-infra-eng@google.com bhthompson@chromium.org
With temporary permission to push the new branch (thanks to Bernie), the new branch , chromeos-5.44,is now in place.

Comment 2 by mcchou@chromium.org, Apr 4 2017

Status: Verified (was: Assigned)

Comment 3 by fbeaufort@chromium.org, Apr 6 2017

Blocking: 708291
►

Sign in to add a comment