From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: Patch series for Kodi 16-Jarvis
Date: Sun, 20 Dec 2015 13:54:12 +0100 [thread overview]
Message-ID: <20151220135412.652a8344@free-electrons.com> (raw)
In-Reply-To: <vjiikcxh6u.ln2@ID-313208.user.individual.net>
Bernd,
On Sun, 20 Dec 2015 13:13:19 +0100, Bernd Kuhls wrote:
> after a first review by Thomas I just updated the branch.
Thanks. I don't know if others will agree, but I believe it might make
things easier to review if all the very simple "bump version" patches
for all kodi add-ons were merged into a single patch. I know we
normally don't do that, but it would make the series a lot shorter, and
would emphasize the few updates for which it's not just a mechanical
bump. So, this "big" commit would only contain the version bumps for
the packages that don't require anything but a change to the version.
If you need to do more than that, then it should be in a separate
commit per package.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-20 12:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 18:05 [Buildroot] RFC: Patch series for Kodi 16-Jarvis Bernd Kuhls
2015-12-20 12:13 ` Bernd Kuhls
2015-12-20 12:54 ` Thomas Petazzoni [this message]
2015-12-20 13:00 ` Yann E. MORIN
2015-12-20 13:16 ` Thomas Petazzoni
2015-12-20 13:48 ` Bernd Kuhls
2015-12-20 14:51 ` Yann E. MORIN
2015-12-20 20:37 ` Bernd Kuhls
2016-01-24 13:44 ` Bernd Kuhls
2016-01-24 14:56 ` Thomas Petazzoni
2016-01-24 15:18 ` Bernd Kuhls
2016-01-31 16:38 ` Bernd Kuhls
2016-02-04 20:39 ` Bernd Kuhls
2016-02-07 13:41 ` Bernd Kuhls
2016-02-07 13:58 ` Thomas Petazzoni
2016-02-13 15:41 ` Bernd Kuhls
2015-12-20 20:41 ` Bernd Kuhls
2015-12-20 14:47 ` Yann E. MORIN
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=20151220135412.652a8344@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