docs/manual: update contribute.txt to cover get-developers
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Mon, 12 Sep 2016 20:54:54 +0000 (22:54 +0200)
committerPeter Korsgaard <peter@korsgaard.com>
Wed, 21 Sep 2016 07:06:08 +0000 (09:06 +0200)
This commit updates the contribute.txt part of the manual to tell
people to use get-developers to get the appropriate "git send-email"
command when sending patches.

[Peter: use --cc instead of --to as suggested by Yann/Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
docs/manual/contribute.txt

index 1b1f4de1967cc26094a9a8aaf872902f1b0cc1d9..d4ec2e11846c288f68d6ffa515c21f7dd4ab2e16 100644 (file)
@@ -283,10 +283,18 @@ automatically adding the +Signed-off-by+ line.
 Once patch files are generated, you can review/edit the commit message
 before submitting them, using your favorite text editor.
 
-Lastly, send/submit your patch set to the Buildroot mailing list:
+Buildroot provides a handy tool to know to whom your patches should be
+sent, called +get-developers+. This tool reads your patches and
+outputs the appropriate +git send-email+ command to use:
 
 ---------------------
-$ git send-email --to buildroot@buildroot.org outgoing/*
+$ ./support/scripts/get-developers outgoing/*
+---------------------
+
+Use the output of +get-developers+ to send your patches:
+
+---------------------
+$ git send-email --to buildroot@buildroot.org --cc bob --cc alice outgoing/*
 ---------------------
 
 Note that +git+ should be configured to use your mail account.