From: Olaf Hering <olh@suse.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cc-version not available to change EXTRA_CFLAGS
Date: Sat, 21 Jan 2006 23:21:25 +0100 [thread overview]
Message-ID: <20060121222125.GA22379@suse.de> (raw)
In-Reply-To: <20060121221249.GB7711@mars.ravnborg.org>
On Sat, Jan 21, Sam Ravnborg wrote:
> I can try to move them to Kbuild.include - that should fix this usecase.
Thanks.
--
short story of a lazy sysadmin:
alias appserv=wotan
next prev parent reply other threads:[~2006-01-21 22:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 18:08 cc-version not available to change EXTRA_CFLAGS Olaf Hering
2006-01-21 22:12 ` Sam Ravnborg
2006-01-21 22:21 ` Olaf Hering [this message]
2006-01-21 22:57 ` Sam Ravnborg
2006-01-21 23:15 ` Olaf Hering
2006-01-21 23:25 ` Sam Ravnborg
2006-01-23 11:02 ` Olaf Hering
2006-02-10 19:47 ` Olaf Hering
2006-02-18 9:03 ` Sam Ravnborg
2006-07-19 9:02 ` Olaf Hering
2006-07-23 17:51 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2006-01-21 19:07 Andrey Borzenkov
2006-01-21 19:11 ` Olaf Hering
2006-01-21 19:47 ` Andrey Borzenkov
2006-01-21 21:07 ` Olaf Hering
2006-01-21 22:51 ` Jan Engelhardt
2006-01-21 23:00 ` 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=20060121222125.GA22379@suse.de \
--to=olh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.