Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next] get-developers: add option to get developers for files
Date: Mon, 14 Aug 2017 22:42:25 +0200	[thread overview]
Message-ID: <20170814224225.6d81a2e8@windsurf> (raw)
In-Reply-To: <20170810211116.7996-1-arnout@mind.be>

Hello,

On Thu, 10 Aug 2017 23:11:16 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> The DEVELOPERS file lists file patterns, but the get-developers script
> only supports getting packages and CPU architectures. Some files are
> neither of those, e.g. defconfigs, support files, package infras, ...
> 
> Add a '-f' option that allows to give a list of files for which to get
> the developer(s).
> 
> Note that the DEVELOPERS file contains directories as well as files,
> and the directories are not expanded into individual files. Therefore,
> we have to use f.startswith(devfile) to match a directory. This assumes
> that the directory name ends with /, otherwise 'package/python' would
> also match 'package/python-foo'. Since we make sure that directories do
> end with / in the DEVELOPERS file, and since false positives are not
> much of an issue in this case, this isn't a problem.
> 
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
>  utils/get-developers | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)

Applied to next, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2017-08-14 20:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10 21:11 [Buildroot] [PATCH/next] get-developers: add option to get developers for files Arnout Vandecappelle
2017-08-14 20:42 ` 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=20170814224225.6d81a2e8@windsurf \
    --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