All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Martincoski <ricardo.martincoski@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 5/5] support/scripts/pkgstats: add CPE reporting
Date: Fri, 18 May 2018 00:44:24 -0300	[thread overview]
Message-ID: <5afe4c1839fcf_1eae2ae8fa169d84698de@ultri5.mail> (raw)
In-Reply-To: CANQCQpYhWzrvpbRqfVm__nrdGe7_ThfW9smmCD4CKSBKk4ySwg@mail.gmail.com

Hello,

On Fri, May 18, 2018 at 12:21 AM, Matthew Weber wrote:

> I caught Arnout on IRC today and my v5 patchset reflects his
> suggestion.  Ended up calling the class/module file
> support/scripts/cpedb.py and support/scripts/cpe-report for the

Good names IMO.

Just for reference, in the same machine with v5 takes 3m13,630s to run pkg-stats.
In the current master: 1m40,318s

> checker script.  I do see what you mean about a user facing script.
> What do others think?

Let's wait for more input.

But if for any reason you send a v6, I would suggest to:
Merge patch 7 back to 5.
Split patch 6 into one changing print to print(), and another one
adding CPE report.

Regards,
Ricardo

  reply	other threads:[~2018-05-18  3:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10 18:58 [Buildroot] [PATCH v4 0/5] CPE ID Support Matt Weber
2018-05-10 18:58 ` [Buildroot] [PATCH v4 1/5] cpe-info: new make target Matt Weber
2018-05-10 18:58 ` [Buildroot] [PATCH v4 2/5] cpe-info: id prefix/suffix Matt Weber
2018-05-10 18:58 ` [Buildroot] [PATCH v4 3/5] cpe-info: only report target pkgs Matt Weber
2018-05-10 18:58 ` [Buildroot] [PATCH v4 4/5] cpe-info: update manual for new pkg vars Matt Weber
2018-05-10 18:58 ` [Buildroot] [PATCH v4 5/5] support/scripts/pkgstats: add CPE reporting Matt Weber
2018-05-16  3:43   ` Ricardo Martincoski
2018-05-16 23:32     ` Arnout Vandecappelle
2018-05-17  1:42       ` Matthew Weber
2018-05-18  3:16         ` Ricardo Martincoski
2018-05-18  3:21           ` Matthew Weber
2018-05-18  3:44             ` Ricardo Martincoski [this message]
2018-05-18 13:07               ` Matthew Weber
2018-05-18  3:07       ` Ricardo Martincoski
2018-05-18  3:18         ` Matthew Weber
2018-05-16 23:34   ` Arnout Vandecappelle
2018-05-17  1:42     ` Matthew Weber

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=5afe4c1839fcf_1eae2ae8fa169d84698de@ultri5.mail \
    --to=ricardo.martincoski@gmail.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.