Date: Mon, 13 Mar 2006 10:12:54 +0100
From: Sam Ravnborg <sam@ravnborg.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
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...
Message-ID: <20060313091254.GA28231@mars.ravnborg.org>
References: <20060312172511.GA17936@vana.vc.cvut.cz> <20060312174250.GA1470@mars.ravnborg.org> <44150CD7.604@yahoo.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <44150CD7.604@yahoo.com.au>
User-Agent: Mutt/1.5.11
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1012
Lines: 25

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.

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/