From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 4/4] docs/manual: add new section about the DEVELOPERS file and get-developer
Date: Wed, 21 Sep 2016 09:17:45 +0200 [thread overview]
Message-ID: <871t0dzppi.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1473713695-2611-5-git-send-email-thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Mon, 12 Sep 2016 22:54:55 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> docs/manual/contribute.txt | 6 ++++++
> docs/manual/developers.txt | 46 ++++++++++++++++++++++++++++++++++++++++++++++
> docs/manual/manual.txt | 2 ++
> 3 files changed, 54 insertions(+)
> create mode 100644 docs/manual/developers.txt
> diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt
> index 2973ef7..a8f9db7 100644
> --- a/docs/manual/contribute.txt
> +++ b/docs/manual/contribute.txt
> @@ -258,6 +258,12 @@ removed, preferably with the upstream commit ID. Also any other
> required changes should be explained explicitly, like configure
> options that no longer exist or are no longer needed.
> +If you are interested in getting notified of build failures and of
> +further changes in the packages you added or modified, please add
> +yourself to the DEVELOPERS file. This should be done in a separate
> +patch of the series. See xref:DEVELOPERS[the DEVELOPERS file] for more
> +information.
Committed after tweaking the wording and adding an xref like suggested
by Arnout, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-09-21 7:17 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
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 [this message]
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=871t0dzppi.fsf@dell.be.48ers.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox