Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/xbmc: Bump version to 13.2rc1
Date: Wed, 13 Aug 2014 09:25:18 +0200	[thread overview]
Message-ID: <20140813092518.4d70cd10@free-electrons.com> (raw)
In-Reply-To: <1407906206-7513-1-git-send-email-bernd.kuhls@t-online.de>

Peter,

On Wed, 13 Aug 2014 07:03:26 +0200, Bernd Kuhls wrote:
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
>  package/xbmc/xbmc.mk |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/xbmc/xbmc.mk b/package/xbmc/xbmc.mk
> index a7c8080..eaa21c9 100644
> --- a/package/xbmc/xbmc.mk
> +++ b/package/xbmc/xbmc.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -XBMC_VERSION = 13.2b3-Gotham
> +XBMC_VERSION = 13.2rc1-Gotham
>  XBMC_SOURCE = $(XBMC_VERSION).tar.gz
>  XBMC_SITE = https://github.com/xbmc/xbmc/archive
>  XBMC_LICENSE = GPLv2

If you commit this, then I suggest it goes to 'master' and not 'next'.
While we normally merge version bumps in 'next' at this point, this
version bump is a bump from a "beta" version to a "release candidate"
version, so it should normally bring more stability/fixes to XBMC.

Bernd: it would have been good to have made this explicit in the commit
log.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-08-13  7:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13  5:03 [Buildroot] [PATCH] package/xbmc: Bump version to 13.2rc1 Bernd Kuhls
2014-08-13  7:25 ` Thomas Petazzoni [this message]
2014-08-13 11:58   ` Yann E. MORIN
2014-08-14  8:05     ` Peter Korsgaard
2014-08-14  8:04 ` Peter Korsgaard

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=20140813092518.4d70cd10@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