From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv5 3/4] Makefile: implement a size-stats target
Date: Thu, 3 Sep 2015 14:21:27 +0200 [thread overview]
Message-ID: <20150903142127.528cbc63@free-electrons.com> (raw)
In-Reply-To: <20150903102905.GC3689@free.fr>
Dear Yann E. MORIN,
On Thu, 3 Sep 2015 12:29:05 +0200, Yann E. MORIN wrote:
> Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Thanks!
> I would however have called this something like graph-sizes, so it is in
> line with the other graph-generating targets.
It used to be called graph-size, until I changed the code to also
generate CSV files. So now it doesn't generate just a graph, but also
raw CSV data, which is why I changed to size-stats. If despite that
you think "make graph-size" remains a better naming, I'm fine with
changing back.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-03 12:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 21:15 [Buildroot] [PATCHv5 0/4] Generate package size statistics Thomas Petazzoni
2015-09-02 21:15 ` [Buildroot] [PATCHv5 1/4] pkg-generic: add step_pkg_size global instrumentation hook Thomas Petazzoni
2015-09-03 10:25 ` Yann E. MORIN
2015-09-09 13:11 ` Vicente Olivert Riera
2015-09-09 13:46 ` Thomas Petazzoni
2015-09-09 13:50 ` Vicente Olivert Riera
2015-09-09 14:10 ` Thomas Petazzoni
2015-09-02 21:15 ` [Buildroot] [PATCHv5 2/4] support/scripts: add size-stats script Thomas Petazzoni
2015-09-03 10:27 ` Yann E. MORIN
2015-09-02 21:15 ` [Buildroot] [PATCHv5 3/4] Makefile: implement a size-stats target Thomas Petazzoni
2015-09-03 10:29 ` Yann E. MORIN
2015-09-03 12:21 ` Thomas Petazzoni [this message]
2015-09-03 12:36 ` Yann E. MORIN
2015-09-02 21:15 ` [Buildroot] [PATCHv5 4/4] docs/manual: add section about size graphing Thomas Petazzoni
2015-09-03 10:37 ` Yann E. MORIN
2015-09-03 10:43 ` Yann E. MORIN
2015-09-15 2:54 ` Ryan Barnett
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=20150903142127.528cbc63@free-electrons.com \
--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