All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] docs/manual: document the new get-developers -e option
Date: Tue, 9 Oct 2018 14:48:07 +0200	[thread overview]
Message-ID: <20181009130112.2A8D18E60D@busybox.osuosl.org> (raw)

commit: https://git.buildroot.net/buildroot/commit/?id=507d56a6be67b7b4e5c40b55c2e56ffbb4ff0386
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Explain how this can be used with git send-email, and how git can be
configured to use it automatically.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
 docs/manual/contribute.txt | 22 ++++++++++++++++++++++
 docs/manual/developers.txt |  3 ++-
 2 files changed, 24 insertions(+), 1 deletion(-)

diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt
index b531ea987e..60bfb961f0 100644
--- a/docs/manual/contribute.txt
+++ b/docs/manual/contribute.txt
@@ -308,6 +308,28 @@ Use the output of +get-developers+ to send your patches:
 $ git send-email --to buildroot at buildroot.org --cc bob --cc alice outgoing/*
 ---------------------
 
+Alternatively, +get-developers -e+ can be used directly with the
++--cc-cmd+ argument to +git send-email+ to automatically CC the
+affected developers:
+
+---------------------
+$ git send-email --to buildroot at buildroot.org \
+      --cc-cmd './utils/get-developers -e' origin/master
+---------------------
+
++git+ can be configured to automatically do this out of the box with:
+
+---------------------
+$ git config sendemail.to buildroot at buildroot.org
+$ git config sendemail.ccCmd "$(pwd)/utils/get-developers -e"
+---------------------
+
+And then just do:
+
+---------------------
+$ git send-email origin/master
+---------------------
+
 Note that +git+ should be configured to use your mail account.
 To configure +git+, see +man git-send-email+ or google it.
 
diff --git a/docs/manual/developers.txt b/docs/manual/developers.txt
index a0a3668dbc..0da499e100 100644
--- a/docs/manual/developers.txt
+++ b/docs/manual/developers.txt
@@ -31,7 +31,8 @@ the +DEVELOPERS+ file for various tasks:
 
 - When passing one or several patches as command line argument,
   +get-developer+ will return the appropriate +git send-email+
-  command.
+  command. If the +-e+ option is passed, only the email addresses are
+  printed in a format suitable for +git send-email --cc-cmd+.
 
 - When using the +-a <arch>+ command line option, +get-developer+ will
   return the list of developers in charge of the given architecture.

                 reply	other threads:[~2018-10-09 12:48 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=20181009130112.2A8D18E60D@busybox.osuosl.org \
    --to=thomas.petazzoni@bootlin.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.