From: Tejun Heo <htejun@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Petr Vandrovec <petr@vandrovec.name>,
linux-kernel@vger.kernel.org, sam@ravenborg.org,
kai@germaschewski.name
Subject: Re: [PATCH] Do not rebuild full kernel tree again and again...
Date: Fri, 17 Mar 2006 03:31:06 +0900 [thread overview]
Message-ID: <4419AEEA.50702@gmail.com> (raw)
In-Reply-To: <20060313163041.GA29719@mars.ravnborg.org>
Sam Ravnborg wrote:
> On Mon, Mar 13, 2006 at 09:47:08PM +1100, Nick Piggin wrote:
> >>I'm seeing this behaviour too in -rc6 and it is a bad regression
>
>>>>for a developer. I assume there will be some workaround?
>>>
>>>I assume debian soon will update make to current version from CVS that
>>>has this behaviour removed.
>>>
>>
>>So long as it just requires a tools update then that's fine for me.
>
> I should note here that it was agreed with Paul that upcoming make
> relase will not have this change, but next release will have it.
> So 2.6.17 kbuild will take care of being forward compatible in this
> matter.
>
Wouldn't it be better to have an option to tell make to assume the old
behavior? I only skimmed the original thread but it didn't seem terribly
complex thing to do. A LOT of people will be doing things on pre-2.6.17
kernel for quite some time and they will be cursing a lot if they have
to rebuild everything everytime.
Thanks.
--
tejun
next prev parent reply other threads:[~2006-03-16 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 17:25 [PATCH] Do not rebuild full kernel tree again and again Petr Vandrovec
2006-03-12 17:42 ` Sam Ravnborg
2006-03-13 6:10 ` Nick Piggin
2006-03-13 9:12 ` Sam Ravnborg
2006-03-13 10:47 ` Nick Piggin
2006-03-13 16:30 ` Sam Ravnborg
2006-03-16 18:31 ` Tejun Heo [this message]
2006-03-16 18:37 ` Sam Ravnborg
2006-03-16 19:06 ` Tejun Heo
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=4419AEEA.50702@gmail.com \
--to=htejun@gmail.com \
--cc=kai@germaschewski.name \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=petr@vandrovec.name \
--cc=sam@ravenborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox