Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Schoenert <c.schoenert@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 00/10] [reworked] Updating directfb and divine
Date: Sun, 10 Mar 2013 19:32:41 +0100	[thread overview]
Message-ID: <1362940371-25899-1-git-send-email-c.schoenert@gmail.com> (raw)

From: Carsten Schoenert <c.schoenert@gmail.com>

Hello,

after the reviewing of my previous patches by Thomas I have reworked
those patches. After some tests related to the dependencies of other
packages on directfb I expanded my patch series because of broken
dependencies by the newer directfb version.

The packages directfb-exambles and sawman are bumped to current versions
so the packages are buildable against the newer directfb version.
The Qt package I doesn't have tested.

I added new entrys into Config.in.legacy for the renamed BR2 variables.
Hopefully in the correct format.

If something is still wrong please let me know.

Regards
Carsten

Carsten Schoenert (10):
  directfb: bumping version to 1.6.3
  divine: bumping version to 1.6.3
  directfb: expanding the help strings
  directfb: fixing typo in variables
  Config.in.legacy: adding renamed BR2 Options
  directfb-examples: correcting indentation and expanding help text
  directfb-examples: bump to version 1.6.0
  directfb-exambles: adding new examples to the menu
  directfb-examples: adding license information
  sawman: bumping version to 1.6.3

 Config.in.legacy                               |   18 +++
 package/directfb-examples/Config.in            |  186 +++++++++++++++++-------
 package/directfb-examples/directfb-examples.mk |    6 +-
 package/directfb/Config.in                     |   15 +-
 package/directfb/directfb.mk                   |    8 +-
 package/divine/divine.mk                       |   11 +-
 package/sawman/sawman.mk                       |    2 +-
 7 files changed, 185 insertions(+), 61 deletions(-)

-- 
1.7.10.4

             reply	other threads:[~2013-03-10 18:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-10 18:32 Carsten Schoenert [this message]
2013-03-10 18:32 ` [Buildroot] [PATCH 01/10] directfb: bumping version to 1.6.3 Carsten Schoenert
2013-03-10 18:32 ` [Buildroot] [PATCH 02/10] divine: " Carsten Schoenert
2013-03-10 18:32 ` [Buildroot] [PATCH v2 03/10] directfb: expanding the help strings Carsten Schoenert
2013-03-10 18:32 ` [Buildroot] [PATCH 04/10] directfb: fixing typo in variables Carsten Schoenert
2013-03-10 18:32 ` [Buildroot] [PATCH 05/10] Config.in.legacy: adding renamed BR2 Options Carsten Schoenert
2013-04-28 20:36   ` Peter Korsgaard
2013-03-10 18:32 ` [Buildroot] [PATCH 06/10] directfb-examples: correcting indentation and expanding help text Carsten Schoenert
2013-03-10 18:32 ` [Buildroot] [PATCH 07/10] directfb-examples: bump to version 1.6.0 Carsten Schoenert
2013-03-10 18:32 ` [Buildroot] [PATCH 08/10] directfb-exambles: adding new examples to the menu Carsten Schoenert
2013-03-10 18:32 ` [Buildroot] [PATCH 09/10] directfb-examples: adding license information Carsten Schoenert
2013-03-10 18:32 ` [Buildroot] [PATCH 10/10] sawman: bumping version to 1.6.3 Carsten Schoenert
2013-04-28 20:36 ` [Buildroot] [PATCH 00/10] [reworked] Updating directfb and divine 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=1362940371-25899-1-git-send-email-c.schoenert@gmail.com \
    --to=c.schoenert@gmail.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