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

Clone this repo:
  1. 6d5abca Add base/notreached.h for NOTREACHED(). by Qijiang Fan · 3 weeks ago main release-R91-13904.B stabilize-13895.B stabilize-coil-13902.B stabilize-glibc-13901.B
  2. 6ffaf0f cbor: use unversioned libchrome libraray. by Qijiang Fan · 6 months ago factory-dedede-13683.B factory-puff-13813.B factory-test-13683.B factory-volteer-13600.B factory-zork-13700.B firmware-asurada-13885.B firmware-dedede-13606.B firmware-quiche-13883.B firmware-trogdor-13577.B firmware-volteer-13672.39.B firmware-volteer-13672.47.B firmware-volteer-13672.81.B firmware-volteer-13672.B master release-R88-13597.B release-R89-13729.B release-R90-13816.B stabilize-13591.B stabilize-13597.103.B stabilize-13597.105.B stabilize-13597.66.B stabilize-13597.67.B stabilize-13597.68.B stabilize-13597.69.B stabilize-13597.70.B stabilize-13597.71.B stabilize-13597.84.B stabilize-13597.85.B stabilize-13597.90.B stabilize-13597.94.B stabilize-13597.95.B stabilize-13597.97.B stabilize-13605.B stabilize-13654.B stabilize-13729.16.B stabilize-13729.45.B stabilize-13729.49.B stabilize-13729.56.B stabilize-13729.57.B stabilize-13729.72.B stabilize-13768.B stabilize-13799.B stabilize-13816.40.B stabilize-13816.51.B stabilize-13816.53.B stabilize-13816.55.B stabilize-13821.B stabilize-13836.B stabilize-13851.B stabilize-13856.B stabilize-ambassador-13597.79.B stabilize-quickfix-13597.30.B stabilize-quickfix-13729.60.B stabilize-quickfix-13729.73.B stabilize-quickfix-13729.84.B stabilize-rust-13562.B stabilize-rust-13613.B stabilize-rust-13720.B stabilize-rust-13776.B stabilize-rust-13795.B stabilize-rust-13836.B
  3. 2f808ca cbor: Update README for new merge instructions by Yicheng Li · 10 months ago factory-puff-13329.B factory-test-13517.B factory-trogdor-13443.B factory-zork-13427.B firmware-puff-13324.B firmware-volteer-13521.B firmware-zork-13421.B firmware-zork-13434.B release-R86-13421.B release-R87-13505.B stabilize-13360.B stabilize-13421.102.B stabilize-13421.103.B stabilize-13421.42.B stabilize-13421.53.B stabilize-13421.73.B stabilize-13421.80.B stabilize-13421.89.B stabilize-13421.96.B stabilize-13421.99.B stabilize-13482.B stabilize-13505.1.B stabilize-13505.100.B stabilize-13505.111.B stabilize-13505.63.B stabilize-13505.65.B stabilize-13505.73.B stabilize-13505.85.B stabilize-13525.B stabilize-13532.B stabilize-quickfix-13421.100.B stabilize-quickfix-13421.74.B stabilize-rust-13514.B stabilize-rust-13555.B
  4. 50b7da8 Merge remote-tracking branch 'cros/upstream/master' by Yicheng Li · 11 months ago factory-endeavour-13295.B release-R85-13310.B stabilize-13310.72.B stabilize-13310.74.B stabilize-13310.83.B stabilize-13310.94.B stabilize-13310.99.B stabilize-lazor-13278.B stabilize-quickfix-13310.73.B stabilize-quickfix-13310.76.B stabilize-quickfix-13310.91.B
  5. 3287dea Remove/replace unnecessary logging.h includes in .cc files (components) by Hans Wennborg · 12 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 (https://chromium.googlesource.com/chromium/src/+/242df8b64d2a0ab5f057d1d4c76ea8537fdbb789) in order to avoid code duplication.

The cros/upstream/master 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 checkout -b upstream cros/upstream/master
  • git checkout master
  • git merge --allow-unrelated-histories upstream
    • Expect merge conflicts, because of the difference in header paths.
    • OWNERS should use the version from master.
    • BUILD.gn should mostly use the version from master, unless the upstream changes the files to be built.
    • The #include paths should use the version from master (without “components/”). This should be the majority of the merge conflicts.
    • In the commit message of the merge, list the changes from upstream that are merged, with original commit hash from upstream.
    • 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.