From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] kconfig [was: Re: svn commit: trunk/buildroot/package/config: lxdialog]
Date: Fri, 29 Jun 2007 10:01:15 +0200 [thread overview]
Message-ID: <20070629080115.GC8033@aon.at> (raw)
In-Reply-To: <08be01c7b9c5$9dedc610$6e02a8c0@k2>
On Thu, Jun 28, 2007 at 03:48:00PM -0500, Rick Foos wrote:
>I was also updating config from earlier. Most of it was the same, but when
>I merged yours into my changes, a few things came up to pass along.
>
>The patch is based on the revision 18967
>
>The lxdialog shell script is added as non-executable. so adding
>svn:executable to the lxdialog shell would be good too.
Since we call it via $(shell $(CONFIG_SHELL) ...) it doesn't have to be
executable. Since it is not executable in the kernel it is better not to
rely on it being executable to avoid surprises if it would be updated
later on.
>
>util.c - .kconfig.d should be .config.cmd
What does this solve?
>lkc.h - PACKAGE should be buildroot not linux.
ok.
>lex.zconf.c - line 3 path doesn't exist (scripts/kconfig)
I don't understand. Please elaborate.
>Makefile - fix standalone build, and distclean for mconf
ok.
>Makefile.kconfig - add else rules to LKC_GENPARSER to regenerate from
What does this solve? I do not want to touch this file. If the kernel
folks accept such a patch, we can pull it from them.
>shipped versions.
prev parent reply other threads:[~2007-06-29 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 13:06 [Buildroot] svn commit: trunk/buildroot/package/config: lxdialog aldot at uclibc.org
2007-06-28 20:48 ` Rick Foos
2007-06-29 8:01 ` Bernhard Fischer [this message]
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=20070629080115.GC8033@aon.at \
--to=rep.dot.nop@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