From: Roland McGrath <roland@redhat.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Pavel Machek <pavel@ucw.cz>,
akpm@linux-foundation.org, linux-kbuild@vger.kernel.org
Subject: Re: [patch 11/18] kconfig CROSS_COMPILE option
Date: Sun, 20 Sep 2009 20:53:02 -0700 (PDT) [thread overview]
Message-ID: <20090921035302.CAC2E13F35@magilla.sf.frob.com> (raw)
In-Reply-To: Sam Ravnborg's message of Sunday, 20 September 2009 12:31:09 +0200 <20090920103108.GA26667@merkur.ravnborg.org>
> So when I move that file to include/generated I will break users script
> silently - sigh.
It's a possibility. If so, they will probably have a far easier time
handling a simple change in the location of the file than an entirely
new scheme where there is no simple file that contains the same string.
> Revised patch following your guidelines below.
> Does this look better to you?
Yes, I like it! I wonder if we might want to treat SUBARCH the same
way, though. I'm not sure that matters except for the ARCH=um case,
but there I have the impression it has exactly the same utility as
$ARCH otherwise, so it makes sense to me to treat it similarly.
Thanks,
Roland
next prev parent reply other threads:[~2009-09-21 3:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 19:49 [patch 11/18] kconfig CROSS_COMPILE option akpm
2009-09-19 9:02 ` Sam Ravnborg
2009-09-19 12:19 ` Roland McGrath
2009-09-19 13:13 ` Sam Ravnborg
2009-09-19 23:48 ` Roland McGrath
2009-09-20 10:31 ` Sam Ravnborg
2009-09-21 3:53 ` Roland McGrath [this message]
2009-09-23 7:16 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2009-09-14 21:49 akpm
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=20090921035302.CAC2E13F35@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=pavel@ucw.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox