From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: Patch series for Kodi 16-Jarvis
Date: Thu, 04 Feb 2016 21:39:28 +0100 [thread overview]
Message-ID: <0hpcocxnjs.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: psp1ocx40l.ln2@ID-313208.user.individual.net
Am Sun, 31 Jan 2016 17:38:17 +0100 schrieb Bernd Kuhls:
> Am Sun, 24 Jan 2016 14:44:31 +0100 schrieb Bernd Kuhls:
>
>> Am Sun, 20 Dec 2015 21:37:09 +0100 schrieb Bernd Kuhls:
>>
>>> Am Sun, 20 Dec 2015 15:51:53 +0100 schrieb Yann E. MORIN:
>>>
>>>> As long as it is only a mechanical bump, without change to the .mk
>>>> files, and with n/removed patches (i.e. only the _VERSION variables
>>>> are changed), then yes, a single commit.
>>>
>>> Hi Yann,
>>>
>>> done: https://github.com/bkuhls/buildroot/commits/kodi16
>>>
>>> Regards, Bernd
>>
>> Hi @all:
>>
>> Kodi 16.0-rc1 was released this week, I updated my github repo.
>>
>> Regards, Bernd
>
> Hi @all:
>
> Kodi 16.0-rc2 was released this week, I updated my github repo.
> http://kodi.tv/kodi-16-0-jarvis-release-candidate-2/
>
> Regards, Bernd
Hi,
I just rebased the patch series.
Regards, Bernd
next prev parent reply other threads:[~2016-02-04 20:39 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 [this message]
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=0hpcocxnjs.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.