1c700d20eb
Starting Chromium 67 we should move to libcc+Electron combined build so create-dist shouldn't be needed anymore anyway. |
||
|---|---|---|
| .. | ||
| lib | ||
| README.md | ||
| apply-patches | ||
| bootstrap | ||
| build | ||
| build-clang.py | ||
| cibuild | ||
| cibuild-libchromiumcontent-linux | ||
| cibuild-libchromiumcontent-linux-arm | ||
| cibuild-libchromiumcontent-linux-arm64 | ||
| cibuild-libchromiumcontent-linux-ia32 | ||
| cibuild-libchromiumcontent-linux-mips64el | ||
| cibuild-libchromiumcontent-linux-x64 | ||
| cibuild.ps1 | ||
| create-dist | ||
| disabled-tests.yaml | ||
| docker-install-build-deps.sh | ||
| download | ||
| get-patch | ||
| package-clang.py | ||
| patch.py | ||
| run-gn | ||
| run_tests | ||
| sccache | ||
| update | ||
| upload | ||
README.md
get-patch
Use it to save commits from upstream repositories as patch files.
Examples
- Write commit contents in the patch format to stdout.
$ ./script/get-patch --repo src --commit 8e8216e5
- Create a patch file with a default name if a specified directory.
$ ./script/get-patch --repo src --commit 8e8216e5 --output_dir patches
- Create a patch file with a custom name in the current directory.
$ ./script/get-patch --repo src --commit 8e8216e5 --filename my.patch
- Create a patch file with a custom name in a specified directory.
$ ./script/get-patch --repo src --commit 8e8216e5 --output_dir patches --filename my.patch
- Create patch files with default names in a specified directory.
$ ./script/get-patch --repo src --output_dir patches --commit 8e8216e5 164c37e3
- Create patch files with custom names in a specified directory. Note that number of filenames must match the number of commits.
$ ./script/get-patch --repo src --output_dir patches --commit 8e8216e5 164c37e3 --filename first.patch second.patch