libbrillo: Update the comment in dbus_object.h to reflect API change in ReplyWithError().

ReplyWithError() of DBusMethodResponse<> actually takes 4 parameters
instead of 3, so the comment is updated to reflect this.

BUG=none
TEST=FEATURES=test emerge-eve libbrillo

Change-Id: I8f05956bb3b5db96d9a681ddb98e7c5d46d8d090
Reviewed-on: https://chromium-review.googlesource.com/1518035
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: John  Chen <zuan@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Cr-Mirrored-From: https://chromium.googlesource.com/chromiumos/platform2
Cr-Mirrored-Commit: bfeb9c0779f8dbace4310791e9bc386ab5c4ac06
1 file changed
tree: c996d609a044d17a42aac748927ee5c1357599ba
  1. brillo/
  2. install_attributes/
  3. policy/
  4. libbrillo-462023.gypi
  5. libbrillo-glib.pc.in
  6. libbrillo-test.pc.in
  7. libbrillo.gyp
  8. libbrillo.gypi
  9. libbrillo.pc.in
  10. libinstallattributes.gypi
  11. libpolicy.gypi
  12. libpolicy.ver
  13. OWNERS
  14. platform2_preinstall.sh
  15. PRESUBMIT.cfg
  16. README.md
  17. testrunner.cc
README.md

libbrillo: platform utility library

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.

AOSP Usage

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.