| commit | f41373fa43888a85114dcbdf14e680aae26776de | [log] [tgz] |
|---|---|---|
| author | David 'Digit' Turner <digit@google.com> | Mon Apr 15 10:43:03 2024 +0200 |
| committer | CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 16 05:16:40 2024 +0000 |
| tree | aac75d78e6f3ad40f2f166d8e464c2d6dba3c9c8 | |
| parent | e17a3a2f0f2dec071d660e7307a5c2008c060c33 [diff] |
sync-branch.py: Add cleanup_history command. Add a new command that rewrites the commit messages of the sync branch commits, in order to get rid of Gerrit-specific lines such as `Commit-Queue:` or `Reviewed-on:`, and creates new `Change-Id:` values when the cleanup happens. The original Change-Id is saved as Original-Change-Id in the cleaned up message, to track where the commit comes from. This makes it easier to track the origin of commits in rebase-sync branches. Does not change commit messages without Gerrit lines, so the command can be called multiple times safely. This command is invoked implicitly by the 'create' command, but since the latter can fail in rare cases during its 'cherry-pick' step, allow it to be invoked manually by the developer after manual conflict resolution is performed. + Change the development branch to 'main', since 'fuchsia-rfc-0153' is no longer used. Change-Id: Id4d3ee742481afa7b8a03274876e78b276001e50 Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/github.com/ninja-build/ninja/+/1028212 Reviewed-by: Tyler Mandry <tmandry@google.com> Commit-Queue: David Turner <digit@google.com>
Ninja is a small build system with a focus on speed. https://ninja-build.org/
See the manual or doc/manual.asciidoc included in the distribution for background and more details.
Binaries for Linux, Mac and Windows are available on GitHub. Run ./ninja -h for Ninja help.
Installation is not necessary because the only required file is the resulting ninja binary. However, to enable features like Bash completion and Emacs and Vim editing modes, some files in misc/ must be copied to appropriate locations.
If you're interested in making changes to Ninja, read CONTRIBUTING.md first.
You can either build Ninja via the custom generator script written in Python or via CMake. For more details see the wiki.
./configure.py --bootstrap
This will generate the ninja binary and a build.ninja file you can now use to build Ninja with itself.
cmake -Bbuild-cmake cmake --build build-cmake
The ninja binary will now be inside the build-cmake directory (you can choose any other name you like).
To run the unit tests:
./build-cmake/ninja_test