public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: David Graeff <david.graeff@web.de>
Cc: linux-kbuild@vger.kernel.org, yann.morin.1998@free.fr
Subject: Re: [RFC PATCH 0/2] kconfig: Prepare for Qt based kconfig update to Qt4/Qt5
Date: Tue, 25 Mar 2014 18:53:04 +0100	[thread overview]
Message-ID: <20140325175304.GA3497@ravnborg.org> (raw)
In-Reply-To: <1395760801-27009-1-git-send-email-david.graeff@web.de>

On Tue, Mar 25, 2014 at 04:19:59PM +0100, David Graeff wrote:
> Hi Yann, all,
> 
> with this rfc patch set I would like to reorganize the kconfig directory structure
> in preparation for updating the Qt3 based flavour of kconfig to Qt4/5 and the
> gtk flavour (version 2->3) eventually. I renamed lxdialog to menuconfig and created
> subdirectories for each flavour except the line based one.
> 
> My suggestion is to add a "qconfig" target to the buildsystem for
> beeing consistent with the names of the other targets where the first character provide a hint
> for the used toolkit. And to accommodate the fact that this frontend may also be used on non
> xserver machines. May feel weird to type xconfig on wayland systems. Patch 2 adds that
> target.
> 
> Last time (some month ago) I provided a patch-set containing all changes (buildystem+qt+gtk) at once,
> that didn't worked well.
The patches has not shown up yet. Maybe they are too big?
Remember to use flags to git so we only see the rename and not the full fil in the diff.
-M -P IIRC but I am not sure.

	Sam

  reply	other threads:[~2014-03-25 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <kconfig-port-qt>
2014-03-25 15:19 ` [RFC PATCH 0/2] kconfig: Prepare for Qt based kconfig update to Qt4/Qt5 David Graeff
2014-03-25 17:53   ` Sam Ravnborg [this message]
2014-03-25 15:20 ` [RFC PATCH 1/2] kconfig: Move flavours into their own subdirectories David Graeff
2014-03-25 15:20 ` [RFC PATCH 2/2] kconfig: Add qconfig makefile target additionally to the xconfig target David Graeff

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=20140325175304.GA3497@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=david.graeff@web.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=yann.morin.1998@free.fr \
    /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