commit | ffa32a7560bcb9ab959e0042076d243659c2bf6a | [log] [tgz] |
---|---|---|
author | Xin Li <delphij@google.com> | Mon Apr 29 11:49:56 2024 -0700 |
committer | Xin Li <delphij@google.com> | Mon Apr 29 11:49:56 2024 -0700 |
tree | 158f5f4eba68adeaa20d94d9626b0ff92114be9e | |
parent | 5ed958220babed4fa137bf6afab0dc4d5fb25db8 [diff] | |
parent | b7e85046deeb05a730ccc3750dea2c47dd559129 [diff] |
Empty merge of Android 24Q2 Release (ab/11526283) to aosp-main-future Bug: 337098550 Merged-In: I907a949535002de4c714568cbca85ffe5c015e3c Change-Id: I018ed16c4f9ac41bc249c194660af7ec9f5cf897
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.