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 03/19] package/gnuchess: bump version to 6.2.1
Date: Sun, 26 Apr 2015 14:30:13 +0200	[thread overview]
Message-ID: <20150426143013.3430696c@free-electrons.com> (raw)
In-Reply-To: <1429453778-4178-3-git-send-email-bernd.kuhls@t-online.de>

Dear Bernd Kuhls,

On Sun, 19 Apr 2015 16:29:22 +0200, Bernd Kuhls wrote:
> Removed unneeded patches, Debian did the same:
> http://metadata.ftp-master.debian.org/changelogs/main/g/gnuchess/unstable_changelog
> 
> gnuchess (6.0.2-1) unstable; urgency=low
> 
>   * New upstream version (Closes: #637722)
> [...]
>     - Drop patches
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
>  package/gnuchess/0001-getline-conflicts.patch |   48 -------------------------
>  package/gnuchess/0002-misc-fixes.patch        |   11 ------
>  package/gnuchess/gnuchess.mk                  |    2 +-
>  3 files changed, 1 insertion(+), 60 deletions(-)
>  delete mode 100644 package/gnuchess/0001-getline-conflicts.patch
>  delete mode 100644 package/gnuchess/0002-misc-fixes.patch

Applied after checking why the patch is no longer needed, and adjusting
the commit log accordingly.

Thanks,

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

  parent reply	other threads:[~2015-04-26 12:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-19 14:29 [Buildroot] [PATCH 01/19] package/flickcurl: bump version to 1.26 Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 02/19] package/fmtools: bump version to 2.0.7 Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 03/19] package/gnuchess: bump version to 6.2.1 Bernd Kuhls
2015-04-19 21:25   ` Thomas Petazzoni
2015-04-26 12:30   ` Thomas Petazzoni [this message]
2015-04-19 14:29 ` [Buildroot] [PATCH 04/19] package/hiawatha: bump version to 9.12 Bernd Kuhls
2015-04-19 14:36   ` Gustavo Zacarias
2015-04-22 21:29     ` Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 05/19] package/ftop: add hash Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 06/19] package/gdbm: " Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 07/19] package/ghostscript-fonts: " Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 08/19] package/gtest: " Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 09/19] package/heirloom-mailx: " Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 10/19] package/htop: " Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 11/19] package/hwdata: " Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 12/19] package/iozone: bump to version 3_430 Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 13/19] package/igh-ethercat: add hash Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 14/19] package/input-tools: " Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 15/19] package/intltool: " Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 16/19] package/ipmiutil: " Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 17/19] package/iptraf-ng: " Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 18/19] package/iputils: " Bernd Kuhls
2015-04-19 14:29 ` [Buildroot] [PATCH 19/19] package/jimtcl: " 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=20150426143013.3430696c@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