From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C83CE138680 for ; Fri, 25 Jan 2013 13:44:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E09B0E05FE; Fri, 25 Jan 2013 13:44:03 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EA46EE05EF for ; Fri, 25 Jan 2013 13:44:02 +0000 (UTC) Received: from mail-ob0-f178.google.com (mail-ob0-f178.google.com [209.85.214.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: djc) by smtp.gentoo.org (Postfix) with ESMTPSA id 06E7A33DC12 for ; Fri, 25 Jan 2013 13:44:01 +0000 (UTC) Received: by mail-ob0-f178.google.com with SMTP id eh20so375918obb.9 for ; Fri, 25 Jan 2013 05:44:00 -0800 (PST) X-Received: by 10.182.38.65 with SMTP id e1mr4490742obk.3.1359121440013; Fri, 25 Jan 2013 05:44:00 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Received: by 10.76.90.73 with HTTP; Fri, 25 Jan 2013 05:43:38 -0800 (PST) In-Reply-To: References: <50FFE241.6030107@gentoo.org> From: Dirkjan Ochtman Date: Fri, 25 Jan 2013 14:43:38 +0100 Message-ID: Subject: Re: [gentoo-dev] news item for udev 197-r3 upgrade (yes, I know, it's late) To: Gentoo Development Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: be49c555-5843-4753-b73d-b81bee7bac8b X-Archives-Hash: 78a702c803b6279c18a4b6543379b2f6 On Fri, Jan 25, 2013 at 12:59 PM, Rich Freeman wrote: > I could see making that the default if there is no .config file > present and a new one is being created, and perhaps upstream would > support that since udev is popular. However, make oldconfig is > usually used when you have a .config file and you just want to update > it. In that case I don't think we should be changing settings - what > if a user doesn't want this set? They'd have to remember to manually > unset it every single time they compile a new kernel, as we'd be > "helpfully" changing it back. Ah yeah, I mistakenly assumed that DEVTMPFS was a relatively new option. Cheers, Dirkjan