bcf2ed5cc3
When called with a list of patches, get-developers prints the entire git send-email invocation line: ./utils/get-developers 0001-git-security-bump-to-version-2.16.5.patch git send-email --to buildroot@buildroot.org --cc "Matt Weber <matthew.weber@rockwellcollins.com>" This may be handy when creating an entire patch series and editing a cover letter, but it does mean that this has to be explicitly executed and get-developers cannot be used directly by the --cc-cmd option of git send-email to automatically CC affected developers. So add an -e flag to only let get-developers print the email addresses of the affected developers in the one-email-per-line format expected by git send-email, similar to how get_maintainer.pl works in the Linux kernel. With this and a suitable git configuration: git config sendemail.to buildroot@buildroot.org git config sendemail.ccCmd "$(pwd)/utils/get-developers -e" You can simply do: git send-email master To automatically mail the buildroot list and CC affected developers on patches. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Acked-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> |
||
---|---|---|
.. | ||
checkpackagelib | ||
brmake | ||
check-package | ||
config | ||
diffconfig | ||
genrandconfig | ||
get-developers | ||
getdeveloperlib.py | ||
readme.txt | ||
scancpan | ||
scanpypi | ||
size-stats-compare | ||
test-pkg |
This directory contains various useful scripts and tools for working with Buildroot. You need not add this directory in your PATH to use any of those tools, but you may do so if you want. brmake a script that can be run instead of make, that prepends the date in front of each line, redirects all of the build output to a file ("'br.log' in the current directory), and just outputs the Buildroot messages (those lines starting with >>>) on stdout. Do not run this script for interactive configuration (e.g. menuconfig) or on an unconfigured directory. The output is redirected so you will see nothing. check-package a script that checks the coding style of a package's Config.in and .mk files, and also tests them for various types of typoes. genrandconfig a script that generates a random configuration, used by the autobuilders (http://autobuild.buildroot.org). It selects a random toolchain from support/config-fragments/autobuild and randomly selects packages to build. get-developpers a script to return the list of people interested in a specific part of Buildroot, so they can be Cc:ed on a mail. Accepts a patch as input, a package name or and architecture name. scancpan a script to create a Buildroot package by scanning a CPAN module description. scanpypi a script to create a Buildroot package by scanning a PyPI package description. size-stats-compare a script to compare the rootfs size between two different Buildroot configurations. This can be used to identify the size impact of a specific option, of a set of specific options, or of an update to a newer Buildroot version... test-pkg a script that tests a specific package against a set of various toolchains, with the goal to detect toolchain-related dependencies (wchar, threads...)