linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Petr Baudis <pasky@ucw.cz>
Cc: zippel@linux-m68k.org, linux-kernel@vger.kernel.org,
	kbuild-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/3] Link lxdialog with mconf directly
Date: Mon, 12 Dec 2005 21:40:49 +0100	[thread overview]
Message-ID: <20051212204049.GA7656@mars.ravnborg.org> (raw)
In-Reply-To: <20051212200817.GM10680@pasky.or.cz>

On Mon, Dec 12, 2005 at 09:08:17PM +0100, Petr Baudis wrote:
> > It is only 8 files and prefixing them with lx* would make them
> > stand out compared to the rest. It is not like there is any user planned
> > for the lxdialog functionality in the kernel, and kconfig users outside
> > the kernel I beleive copy lxdialog with rest of kconfig files.
> 
> Ok. I didn't want to pollute scripts/kconfig/ too much, but if it's ok
> by you, I can do it that way. I will submit another series later in the
> evening.
In the end this is Roman's call, not mine.
Keeping the lxdialog functionality close to the users though makes
total sense. We do not have to take special care of dependencies etc.
> 
> > Btw. the work you are doing are clashing with a general cleanup effort
> > of lxdialog I have in -mm at the moment.
> > I received only very limited feedback = looks ok.
> > Integrating principles from your old patch was on my TODO list.
> 
> Do you mean the series you posted at Nov 21? Should I just rebase my
> patches on top of that?
Please do so. I did not post the biggest one where I Lindented all of
lxdialog, but they are all in
git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild.git

> FWIW, the changes there look fine to me. I actually wanted to change the
> indentation of the menus as well; it looks horrible especially in the
> singlemenu mode.
> 
> > I have something in the works that uses linked list instead of a
> > preallocated array, to keep the dynamic behaviour. I will probarly make
> > a version with the linked list approach but otherwise use your changes
> > to mconf.c. But it will take a few days until I get to it.
> 
> I can do it and include it in the updated series.
Would be perfect!

I will then do a proper review of next round of patches.

	Sam

  reply	other threads:[~2005-12-12 20:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-12  0:41 [PATCH 0/3] Link lxdialog with mconf directly Petr Baudis
2005-12-12  0:46 ` [PATCH 1/3] [kbuild] Allow building of standalone .so libraries Petr Baudis
2005-12-12  0:46 ` [PATCH 2/3] [kbuild] Possibility to sanely link against off-directory .so Petr Baudis
2005-12-12  0:46 ` [PATCH 3/3] [kconfig] Direct use of lxdialog routines by menuconfig Petr Baudis
2005-12-12  3:18   ` Kurt Wall
2005-12-12 11:20     ` Petr Baudis
2005-12-13  2:59       ` Kurt Wall
2005-12-14 22:18   ` Roman Zippel
2005-12-16 20:29     ` Sam Ravnborg
2005-12-14 22:57   ` Jesper Juhl
2005-12-12 19:14 ` [PATCH 0/3] Link lxdialog with mconf directly Sam Ravnborg
2005-12-12 20:08   ` Petr Baudis
2005-12-12 20:40     ` Sam Ravnborg [this message]
2005-12-16 21:26     ` Sam Ravnborg

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=20051212204049.GA7656@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pasky@ucw.cz \
    --cc=zippel@linux-m68k.org \
    /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;
as well as URLs for NNTP newsgroup(s).