Fork of chromium/src.git/components/cbor/

Clone this repo:
  1. 9e852aa cbor: migrate base or absl optional to std::optional by hscham · 9 weeks ago factory-14778.B factory-firmware-ti50-guc-14778.B main release-R102-14695.B release-R103-14816.B stabilize-14633.B stabilize-14682.B stabilize-14771.B stabilize-14790.B stabilize-14803.B stabilize-14839.B stabilize-voshyr-14637.B
  2. b88c634 README.md: Update merge instructions by Tom Hughes · 5 months ago factory-brya-14517.B factory-cherry-14455.B factory-guybrush-14600.B firmware-brya-14505.B firmware-cherry-14454.B firmware-guybrush-14500.B release-R100-14526.B release-R101-14588.B release-R99-14469.B stabilize-14411.B stabilize-14438.B stabilize-14442.B stabilize-14469.41.B stabilize-14469.58.B stabilize-14469.8.B stabilize-14469.9.B stabilize-14477.B stabilize-14496.B stabilize-14498.B stabilize-14526.57.B stabilize-14526.67.B stabilize-14526.73.B stabilize-14526.84.B stabilize-14526.89.B stabilize-14528.B stabilize-14532.B stabilize-14536.B stabilize-14588.14.B stabilize-14588.98.B stabilize-14589.B stabilize-14616.B stabilize-quickfix-14526.91.B stabilize-wristpin-14469.59.B
  3. 30d2028 Revert "components: Replace base::Optional and friends with absl counterparts" by Tom Hughes · 5 months ago
  4. 04d07c9 Revert "Rewrite most `Foo* field_` pointer fields to `raw_ptr<Foo> field_`." by Tom Hughes · 5 months ago
  5. cabda56 Merge remote-tracking branch 'cros/upstream/main' by Tom Hughes · 6 months ago

cbor: Concise Binary Object Representation

This 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.

How to update the source

To pull in updates from chromium/src, do the following:

  • git remote update

  • git checkout -b main cros/main

  • git merge cros/upstream/main

    • Expect merge conflicts, because of the difference in header paths.
    • 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.
    • The #include paths should use the version from main (without “components/”). This should be the majority of the merge conflicts.
    • In the commit message of the merge, list the commits from upstream that are merged.
    • If you need to do make changes to the merged commits (outside of conflicts), do that work in separate commits. For example, if you need to revert commits, use 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.
    • Check the changes introduced by your merge by doing a diff against the commit before the merge. The difference should be the same as the changes in the upstream.
  • Push the resulting merge commit with:

    (chroot) $ git push HEAD:refs/for/main