From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751092AbWDJJfM (ORCPT ); Mon, 10 Apr 2006 05:35:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751093AbWDJJfM (ORCPT ); Mon, 10 Apr 2006 05:35:12 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:58288 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S1751092AbWDJJfK (ORCPT ); Mon, 10 Apr 2006 05:35:10 -0400 Date: Mon, 10 Apr 2006 11:35:07 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: Andrew Morton cc: linux-kernel@vger.kernel.org, sam@ravnborg.org Subject: Re: [PATCH 0/19] kconfig patches In-Reply-To: <20060410005153.2a5c19e2.akpm@osdl.org> Message-ID: References: <20060409235548.52b563a9.akpm@osdl.org> <20060410005153.2a5c19e2.akpm@osdl.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Mon, 10 Apr 2006, Andrew Morton wrote: > > If you call "make oldconfig", you have to restore the symlink manually. > > Why? What advantage does that have? > > I've been using the copy-it-there approach for maybe four years and have > yet to notice any problem with it. Pretty much every other tool removes the old file before or after creating the new file. This allows it to work with a hardlinked tree, which unfortunately is currently broken for other reasons in kbuild. Could you send me link or a copy of your build tools, which deals with the symlink? bye, Roman