All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] docs/manual: update contribute.txt to cover get-developers
Date: Wed, 21 Sep 2016 09:06:08 +0200	[thread overview]
Message-ID: <20160921071839.D249D7FC9C@busybox.osuosl.org> (raw)

commit: https://git.buildroot.net/buildroot/commit/?id=6017cb8fbd6ea24911fe156c37366ca67278f77f
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master

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 | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt
index 1b1f4de..d4ec2e1 100644
--- a/docs/manual/contribute.txt
+++ b/docs/manual/contribute.txt
@@ -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 at buildroot.org outgoing/*
+$ ./support/scripts/get-developers outgoing/*
+---------------------
+
+Use the output of +get-developers+ to send your patches:
+
+---------------------
+$ git send-email --to buildroot at buildroot.org --cc bob --cc alice outgoing/*
 ---------------------
 
 Note that +git+ should be configured to use your mail account.

                 reply	other threads:[~2016-09-21  7:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160921071839.D249D7FC9C@busybox.osuosl.org \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.