From: Sam Ravnborg <sam@ravnborg.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [RFD] kconfig - introduce cond-source
Date: Sun, 31 Jul 2005 10:45:10 +0200 [thread overview]
Message-ID: <20050731084510.GB8588@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0507310247410.3728@scrub.home>
On Sun, Jul 31, 2005 at 02:50:03AM +0200, Roman Zippel wrote:
> Hi,
>
> On Sun, 31 Jul 2005, Sam Ravnborg wrote:
>
> > In a couple of cases I have had the need to include a Kconfig file only
> > if present.
> > The current 'source' directive works as one would expect. It bails out
> > if the file is missing.
>
> I don't really like it, it's an open invitation to abuse.
> I'd rather like to see the user first, which might need it.
Understood.
I will save this until I have a very good example where I need it.
Sam
prev parent reply other threads:[~2005-07-31 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 22:01 Sam Ravnborg
2005-07-31 0:50 ` Roman Zippel
2005-07-31 8:45 ` Sam Ravnborg [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=20050731084510.GB8588@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®