Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: Patch series for Kodi 16-Jarvis
Date: Sat, 19 Dec 2015 19:05:23 +0100	[thread overview]
Message-ID: <3sigkcxlsq.ln2@ID-313208.user.individual.net> (raw)

Hi,

here you will find my current snapshot for the next Kodi release:
https://github.com/bkuhls/buildroot/tree/kodi16

Current release status is beta4:
http://kodi.tv/kodi-16-0-beta-4-jarvis-is-getting-ready-4/

My tree uses HEAD of the Jarvis branch:
https://github.com/xbmc/xbmc/tree/Jarvis

The first two patches in my series do not depend on the Kodi version 
bump, I am using them with 15.2 already, therefore they precede the Kodi 
version bump:
http://patchwork.ozlabs.org/patch/538512/
http://patchwork.ozlabs.org/patch/538513/

Kodi moved to C++11 so we need gcc >= 4.7:
https://github.com/xbmc/xbmc/pull/6412

I know that hash files are missing, I will add them to the patch series 
of the final bump after the release of Kodi 16.0-Jarvis.

Feedback welcome ;)

Regards, Bernd

             reply	other threads:[~2015-12-19 18:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19 18:05 Bernd Kuhls [this message]
2015-12-20 12:13 ` [Buildroot] RFC: Patch series for Kodi 16-Jarvis 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
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=3sigkcxlsq.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --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