From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 3/4] docs/manual: update contribute.txt to cover get-developers
Date: Mon, 12 Sep 2016 23:09:35 +0200 [thread overview]
Message-ID: <20160912210935.GA15314@free.fr> (raw)
In-Reply-To: <1473713695-2611-4-git-send-email-thomas.petazzoni@free-electrons.com>
Thomas, All,
On 2016-09-12 22:54 +0200, Thomas Petazzoni spake thusly:
> 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.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.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..2973ef7 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 --to bob --to alice outgoing/*
Minor tweak: I'd prefer we use carbon-copy: --cc alice --cc bob
Regards,
Yann E. MORIN.
> ---------------------
>
> Note that +git+ should be configured to use your mail account.
> --
> 2.7.4
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-09-12 21:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 20:54 [Buildroot] [PATCH v3 0/4] Add a get-developers script and database Thomas Petazzoni
2016-09-12 20:54 ` [Buildroot] [PATCH v3 1/4] support/scripts/get-developers: add new script Thomas Petazzoni
2016-09-15 20:28 ` Arnout Vandecappelle
2016-09-21 7:03 ` Peter Korsgaard
2016-09-21 8:50 ` Thomas Petazzoni
2016-09-21 9:25 ` Arnout Vandecappelle
2016-09-12 20:54 ` [Buildroot] [PATCH v3 2/4] DEVELOPERS: add initial list of Buildroot developers Thomas Petazzoni
2016-09-21 7:04 ` Peter Korsgaard
2016-09-12 20:54 ` [Buildroot] [PATCH v3 3/4] docs/manual: update contribute.txt to cover get-developers Thomas Petazzoni
2016-09-12 21:09 ` Yann E. MORIN [this message]
2016-09-15 20:29 ` Arnout Vandecappelle
2016-09-21 7:07 ` Peter Korsgaard
2016-09-12 20:54 ` [Buildroot] [PATCH v3 4/4] docs/manual: add new section about the DEVELOPERS file and get-developer Thomas Petazzoni
2016-09-15 20:35 ` Arnout Vandecappelle
2016-09-21 7:17 ` Peter Korsgaard
2016-09-12 21:14 ` [Buildroot] [PATCH v3 0/4] Add a get-developers script and database Yann E. MORIN
2016-09-12 21:30 ` Thomas Petazzoni
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=20160912210935.GA15314@free.fr \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox