[format-code] Add support for --remove-ordinals.

This is a temporary convenience for people who want to stop using
ordinals in their code without trying to figure out where the formatter
lives.

Change-Id: I6690574a283aa25084d4710dd3981a6f8ba08c4d
1 file changed
tree: 0ef23c18b4a3468ec6c92a42ab36e0f1abb63aca
  1. crash/
  2. dart/
  3. devshell/
  4. editors/
  5. gce/
  6. gdb/
  7. manifest/
  8. memory/
  9. packages/
  10. rust/
  11. sdk/
  12. style/
  13. tests/
  14. third_party/
  15. vim/
  16. youcompleteme/
  17. zsh-completion/
  18. .gitignore
  19. AUTHORS
  20. bootstrap
  21. build-qemu.sh
  22. build-zircon.sh
  23. check-gn-format
  24. colorize_logs
  25. CONTRIBUTING.md
  26. fd.py
  27. fetch-build-artifacts
  28. flog
  29. fx
  30. fx-env.sh
  31. fx-wrapper
  32. generate-intellij-config.py
  33. git-file-tidy
  34. git-fuchsia-review
  35. git_utils.py
  36. gn_to_cmake.py
  37. LICENSE
  38. list-available-packages.py
  39. MAINTAINERS
  40. PATENTS
  41. paths.py
  42. README.md
  43. run-dart-action.py
  44. run-zircon-arm64
  45. run-zircon-x86
  46. start-dhcp-server.sh
  47. update-manifest.go
README.md

Scripts

This repository is for scripts useful when hacking on Fuchsia. This repository should contain scripts that perform tasks spanning multiple repositories. Scripts that only operate within a single repository should live in the relevant repository.

push-package.py

The push-package.py script pushes the files listed in the given manifests files. No checking is performed for incremental changes.

The sample command lines below can be used to build Modular and then push those files to the default device. This assumes you have already booted your device with a version of Fuchsia that contains the most recent version of all other packages. This command line uses the “system_manifest” file from each of the modular directories, such as modular, modular_dev, and modular_tests.

cd $FUCHSIA_DIR
fx build peridot:modular_all
scripts/push-package.py out/debug-x64/package/modular*/system_manifest

fx publish

fx publish will take a package from the build and create a Fuchsia package manager package from a build package. It will then add the package to a local update respository which, by default, is put at ${FUCHSIA_BUILD_DIR}/amber-files. It will also add the package content files to the update repository and name these file after their Merkle Root. If a package name is supplied to fx publish, only that package will be processed. If no name is supplied, all the packages made by the build will be included.