Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/iucode-tool: bump version
Date: Mon, 19 Jan 2015 23:30:11 +0100	[thread overview]
Message-ID: <20150119223011.GH4217@free.fr> (raw)
In-Reply-To: <1419156571-12002-2-git-send-email-bernd.kuhls@t-online.de>

Bernd, All,

On 2014-12-21 11:09 +0100, Bernd Kuhls spake thusly:
> - updated upstream location
>   http://metadata.ftp-master.debian.org/changelogs/contrib/i/iucode-tool/unstable_changelog
>   "iucode-tool (1.0.2-1) unstable; urgency=low
>    [...]
>    * debian/control: update for new upstream location at Gitorious"

Version 1.1.1 is now available, too. Care to update, please?
Add me in Cc when respinning, please, so I don;t miss them and can
review quickly (hopefully).

Regards,
Yann E. MORIN.

> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
>  package/iucode-tool/Config.in      |    2 +-
>  package/iucode-tool/iucode-tool.mk |    4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/iucode-tool/Config.in b/package/iucode-tool/Config.in
> index 8f90350..b996b36 100644
> --- a/package/iucode-tool/Config.in
> +++ b/package/iucode-tool/Config.in
> @@ -6,4 +6,4 @@ config BR2_PACKAGE_IUCODE_TOOL
>  	help
>  	  Intel processor microcode tool
>  
> -	  http://packages.debian.org/source/iucode-tool
> +	  https://gitorious.org/iucode-tool
> diff --git a/package/iucode-tool/iucode-tool.mk b/package/iucode-tool/iucode-tool.mk
> index 081b086..44d49d9 100644
> --- a/package/iucode-tool/iucode-tool.mk
> +++ b/package/iucode-tool/iucode-tool.mk
> @@ -4,8 +4,8 @@
>  #
>  ################################################################################
>  
> -IUCODE_TOOL_VERSION = v1.0.1
> -IUCODE_TOOL_SITE = git://git.debian.org/users/hmh/iucode-tool.git
> +IUCODE_TOOL_VERSION = 1cbd73013cd4c6b2b287f07f6189eef35cb83ca0
> +IUCODE_TOOL_SITE = git://gitorious.org/iucode-tool/iucode-tool.git
>  ifeq ($(BR2_TOOLCHAIN_USES_UCLIBC),y)
>  IUCODE_TOOL_CONF_ENV = LIBS="-largp"
>  IUCODE_TOOL_DEPENDENCIES = argp-standalone
> -- 
> 1.7.10.4
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-01-19 22:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-21 10:09 [Buildroot] [PATCH 1/2] package/intel-microcode: bump version Bernd Kuhls
2014-12-21 10:09 ` [Buildroot] [PATCH 2/2] package/iucode-tool: " Bernd Kuhls
2015-01-19 22:30   ` Yann E. MORIN [this message]
2015-01-24 16:41     ` Bernd Kuhls
2015-01-19 22:28 ` [Buildroot] [PATCH 1/2] package/intel-microcode: " Yann E. MORIN
2015-01-24 16:45   ` Bernd Kuhls

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=20150119223011.GH4217@free.fr \
    --to=yann.morin.1998@free.fr \
    --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