From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: 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: Mon, 13 Mar 2006 21:47:08 +1100 [thread overview]
Message-ID: <44154DAC.6050006@yahoo.com.au> (raw)
In-Reply-To: <20060313091254.GA28231@mars.ravnborg.org>
Sam Ravnborg wrote:
> On Mon, Mar 13, 2006 at 05:10:31PM +1100, Nick Piggin wrote:
>
>>Sam Ravnborg wrote:
>>
>>
>>>This issue has been discussed with Paul D. Smith which also provided
>>>a patch similar to yours.
>>>The patch is in the kbuild queue for 2.6.17.
>>>But we also agreed to postpose this change in make until next stable
>>>release. So if you update your make to latest CVS version you will no
>>>longer see this misbehaviour.
>>>And when 2.6.17 opens up kbuild will be 'fixed' in mainline kernel.
>>>
>>
>>So what's going to be done about 2.6.16?
>>
>>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.
Thanks.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-03-13 10:47 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 [this message]
2006-03-13 16:30 ` Sam Ravnborg
2006-03-16 18:31 ` Tejun Heo
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=44154DAC.6050006@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=kai@germaschewski.name \
--cc=linux-kernel@vger.kernel.org \
--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 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.