All of 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, 13 Feb 2016 16:41:56 +0100	[thread overview]
Message-ID: <4fv3pcxqnk.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20160207145859.4fdc2389@free-electrons.com

Am Sun, 07 Feb 2016 14:58:59 +0100 schrieb Thomas Petazzoni:

> 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.

Hi Thomas,

I marked the whole Kodi series as "deferred" in patchworks to reduce the 
number of patches there. When Kodi 16.0 is finally released I will send 
an updated version with hashes ;)

Regards, Bernd

  reply	other threads:[~2016-02-13 15:41 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
2016-02-13 15:41                         ` Bernd Kuhls [this message]
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=4fv3pcxqnk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.