commit | bb9b65f388a5126d12983a4a5978a6d8cd499fb6 | [log] [tgz] |
---|---|---|
author | Qijiang Fan <fqj@google.com> | Wed Jul 01 03:20:06 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Jul 01 03:20:06 2020 +0000 |
tree | b03c4daf3bbbcdc96829053f727f4d7ea25a36e0 | |
parent | e397af970adf8af92990d480f76110af0fff7c60 [diff] | |
parent | d4ab54f37549cae4f62548313fdea4f1a3041613 [diff] |
Merge commit 'cf6c031ec38f6932125148cdaceb984b07ec5052' into HEAD am: e2e0f82d2c am: d4ab54f375 Original change: https://android-review.googlesource.com/c/platform/external/libbrillo/+/1353562 Change-Id: Ia9ac7d2a6eeb4161711d48a9de1a63191c0cd859
libbrillo is a shared library meant to hold common utility code that we deem useful for platform projects. It supplements the functionality provided by libbase/libchrome since that project, by design, only holds functionality that Chromium (the browser) needs. As a result, this tends to be more OS-centric code.
This project is also used by Update Engine which is maintained in AOSP. However, AOSP doesn't use this codebase directly, it maintains its own libbrillo fork.
To help keep the projects in sync, we have a gsubtree set up on our GoB: https://chromium.googlesource.com/chromiumos/platform2/libbrillo/
This allows AOSP to cherry pick or merge changes directly back into their fork.