Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH buildroot-test 0/4] add support for outdated packages
Date: Thu, 1 Aug 2019 14:42:24 +0200	[thread overview]
Message-ID: <20190801144224.69fde7c4@windsurf.home> (raw)
In-Reply-To: <20190708081406.28215-1-victor.huesca@bootlin.com>

Hello,

As usual, this is good work, glad to see that we're finally getting
e-mail notifications for this. See below for some comments.

On Mon,  8 Jul 2019 10:14:02 +0200
Victor Huesca <victor.huesca@bootlin.com> wrote:

> Victor Huesca (4):
>   utils/daily-mail: add information about version that may need an
>     update
>   utils/daily-mail: allow to print a header for results section
>   utils/daily-mail: add some debug information for the Notification
>     class
>   utils/daily-mail: add multiple argument to ease modularity of the
>     script

The main comment I have about the series is that it's not organized in
the proper order. For example, in PATCH 1/4, you add a new argument to
global_email(), which is not used anywhere.

I think you should instead introduce argparse, with just the --dry-run
option first. Then introduce the --branches option in one commit, then
introduce the --date option in another commit, then introduce the
--global-only and --dev-only options in another commit. Then the
introduction of the outdated changes stuff. I.e, really split
independent changes in separate commits.

Speaking of global-only and dev-only, perhaps we should do something
nicer, such as:

	--dest=dev,global --data=autobuild,outdated,defconfig,tests

It allows to select any combination of information and recipient, and
seems a bit more flexible.

But this can be done later. However, I'd really like to have separate
commits for the separate things.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2019-08-01 12:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08  8:14 [Buildroot] [PATCH buildroot-test 0/4] add support for outdated packages Victor Huesca
2019-07-08  8:14 ` [Buildroot] [PATCH buildroot-test 1/4] utils/daily-mail: add information about version that may need an update Victor Huesca
2019-08-01 12:57   ` Thomas Petazzoni
2019-07-08  8:14 ` [Buildroot] [PATCH buildroot-test 2/4] utils/daily-mail: allow to print a header for results section Victor Huesca
2019-08-01 12:58   ` Thomas Petazzoni
2019-07-08  8:14 ` [Buildroot] [PATCH buildroot-test 3/4] utils/daily-mail: add some debug information for the Notification class Victor Huesca
2019-08-01 12:59   ` Thomas Petazzoni
2019-07-08  8:14 ` [Buildroot] [PATCH buildroot-test 4/4] utils/daily-mail: add multiple argument to ease modularity of the script Victor Huesca
2019-08-01 13:01   ` Thomas Petazzoni
2019-08-01 12: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=20190801144224.69fde7c4@windsurf.home \
    --to=thomas.petazzoni@bootlin.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