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

Issue 602348 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature

Blocking:
issue 600655



Sign in to add a comment

Create a new branch for chromiumos/third_party/bluez 5.39 update

Project Member Reported by mcchou@chromium.org, Apr 11 2016

Issue description

A new branch is needed for updating BlueZ to 5.39. The new branch should be created based on the Linux BlueZ upstream 5.39 release, and Chromium-specific patches will be applied on top of the new branch.

repo:
    chromiumos/third_party/bluez

branching source:
    BlueZ upstream

name of the new branch:
    chromeos-5.39

starting git sha1:
commit 969cc06e08d613f58b113bbc60c2ba25dfda3b25
Author: Marcel Holtmann <marcel@holtmann.org>
Date:   Tue Apr 5 00:15:47 2016 +0200

    Release 5.39
 

Comment 1 by vapier@chromium.org, Apr 11 2016

Cc: vapier@chromium.org
Owner: d...@chromium.org

Comment 2 by d...@chromium.org, Apr 12 2016

Status: Fixed (was: Available)
I'm not sure who usually does this, but the only group that has all of the required permissions is mdb/chromeos-branch-creators, which I am not a member of.

I am, however, a Git admin, so I went ahead and created your branch: https://chromium.googlesource.com/chromiumos/third_party/bluez/+/chromeos-5.39

Next time please ping a branch creator.
Status: Verified (was: Fixed)

Sign in to add a comment