commit | 419813738813cd7af9a3d0da43dce410d978a99b | [log] [tgz] |
---|---|---|
author | Helmut Januschka <helmut@januschka.com> | Wed May 01 20:04:48 2024 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 26 07:41:59 2024 |
tree | 7fd8d68411aa4a7449df17f7edf7db198402ecd6 | |
parent | 22ce639d21a6607f23d0c1893a12550613164a83 [diff] |
Convert base::StringPiece to std::string_view This is a cherry-pick of CL:5501048 BUG=b:313545923 TEST=CQ Change-Id: I0843817563cf59a8dd5c32706390b4b51a607abd Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/cbor/+/5740578 Reviewed-by: Firas Sammoura <fsammoura@google.com> Tested-by: Ryo Hashimoto <hashimoto@chromium.org> Commit-Queue: Ryo Hashimoto <hashimoto@chromium.org>
cbor
: Concise Binary Object RepresentationThis library is a partial implementation of the RFC 7049 Concise Binary Object Representation standard.
The source code was fetched from chromium/src
in order to avoid code duplication.
The cros/upstream/main
branch is a mirror of the components/cbor
directory from upstream. It is automatically updated to reflect the latest changes in upstream.
To pull in updates from chromium/src
, do the following:
git remote update
git checkout -b main cros/main
git merge cros/upstream/main
OWNERS
should use the version from main
.BUILD.gn
should mostly use the version from main
, unless the upstream changes the files to be built.#include
paths should use the version from main
(without “components/”). This should be the majority of the merge conflicts.git revert
after committing the merge commit. This preserves the history and makes it clear why a change is being reverted rather than quietly changing it in the merge commit.Push the resulting merge commit with:
(chroot) $ git push HEAD:refs/for/main