Google Git
Sign in
cos / mirrors / cros / chromiumos / platform / dev-util / refs/heads/stabilize-15511.B / . / contrib
tree: 9f88634eb3ffb185e44b46a849f87848fb480158 [path history] [tgz]
  1. branch_tools/
  2. chameleon/
  3. chromium_metadata/
  4. coil_urls/
  5. contrib/
  6. copybot/
  7. corp-ssh-helper-helper/
  8. cros_openwrt/
  9. cvetriager/
  10. emacs/
  11. fflash/
  12. findmissing/
  13. firmware/
  14. forklift/
  15. gfx/
  16. kernel-rebase/
  17. labtunnel/
  18. lium/
  19. net-auditor-parser/
  20. power_measurement/
  21. refactor/
  22. refactor-libchrome/
  23. roafteriniter/
  24. sshwatcher/
  25. syz-repro-automation/
  26. syzbot-autotriager/
  27. variant/
  28. arm_trusted_firmware_uprev
  29. cargo2ebuild.py
  30. cleanup_crates.py
  31. common.sh
  32. cros_check_firmware_tarball
  33. cros_unibuild_convert.py
  34. cros_update_firmware
  35. device_summary.sh
  36. dut-console
  37. feedback-unpack
  38. findfix.py
  39. force_chrome_binpkg.py
  40. forward_usb_devices.py
  41. fromupstream.py
  42. gbatch
  43. gen_uprev_msg.py
  44. get_binhost.py
  45. get_local_manifest
  46. git-clean-refs
  47. graphviz_overlays.py
  48. kernel_decode_stack
  49. merge-kernel
  50. mod_recovery_for_decryption.sh
  51. OWNERS
  52. power_qual_compare.py
  53. README.md
  54. repo-patch
  55. search_blocked_words.sh
  56. servoinfo
  57. setup_cros_cargo_home
  58. shflags
  59. update_aosp.sh
  60. update_gpu_drivers.sh
  61. update_program_fw
  62. uprev_firmware.sh
  63. uprev_scp_firmware.sh
  64. upstream_diff.py
  65. willis.go
contrib/README.md

Unsupported Chrome OS dev scripts

This directory is a place that developers can put scripts that are useful to them and that might be useful to other developers.

A few notes about what's here:

  • Nothing here may be used by build scripts. It's expected to only contain scripts that are run manually.
  • Nobody in the build team maintains these files. If something is broken, you can try using the git history to find someone to help you, but even better you should upload a fix yourself.
  • Chrome OS infrastructure makes no promises to keep scripts in here working. AKA: if you rely on some tool in “chromite”, or on some Google server, or something else official. ...and if that thing changes in a way that breaks you. ...then it's up to you to change your script. The change that broke you will not be reverted.

That being said: enjoy.