From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: Patch series for Kodi 16-Jarvis
Date: Sun, 7 Feb 2016 14:58:59 +0100 [thread overview]
Message-ID: <20160207145859.4fdc2389@free-electrons.com> (raw)
In-Reply-To: <e4ujocxnoh.ln2@ID-313208.user.individual.net>
Dear Bernd Kuhls,
(Please try to Cc: me explicitly on such questions, otherwise I miss
them.)
On Sun, 07 Feb 2016 14:41:02 +0100, Bernd Kuhls wrote:
> right now I am preparing the updated patch series for Kodi 16.0 rc3 which
> was released this week. Because I do not expect any changes to my patch
> series when 16.0 is finally released I would like to ask if you accept
> the Kodi rc3 patch series before buildroot enters rc1 state with the
> final version bump (and addition of hash files, of course ;)) in the next
> weeks?
Are we sure that Kodi 16.0 will be released by the end of February ? If
that's the case, then I think I'm OK with taking the -rc3 patches right
now, and then bump to 16.0 when it gets released, before we
release 2016.02.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-07 13:58 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
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 [this message]
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=20160207145859.4fdc2389@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