From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] DEVELOPERS: fix after moving scripts to utils/ directory
Date: Sat, 1 Jul 2017 19:44:39 +0200 [thread overview]
Message-ID: <20170701194439.555fbf0c@windsurf.home> (raw)
In-Reply-To: <20170701164041.5515-1-arnout@mind.be>
Hello,
On Sat, 1 Jul 2017 18:40:39 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> There were still references to support/scripts/ for scripts that have
> moved to the utils directory. There were also references that were
> updated, but not re-updated when the tools moves to utils.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
> ---
> DEVELOPERS | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
All three patches applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-07-01 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 16:40 [Buildroot] [PATCH 1/3] DEVELOPERS: fix after moving scripts to utils/ directory Arnout Vandecappelle
2017-07-01 16:40 ` [Buildroot] [PATCH 2/3] manual: update old references to support/scripts Arnout Vandecappelle
2017-07-01 16:50 ` Yann E. MORIN
2017-07-01 16:40 ` [Buildroot] [PATCH 3/3] scancpan: update old reference " Arnout Vandecappelle
2017-07-01 16:51 ` Yann E. MORIN
2017-07-01 16:49 ` [Buildroot] [PATCH 1/3] DEVELOPERS: fix after moving scripts to utils/ directory Yann E. MORIN
2017-07-01 17:44 ` Thomas Petazzoni [this message]
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=20170701194439.555fbf0c@windsurf.home \
--to=thomas.petazzoni@free-electrons.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