public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dirkjan Ochtman <djc@gentoo.org>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] news item for udev 197-r3 upgrade (yes, I know, it's late)
Date: Fri, 25 Jan 2013 14:43:38 +0100	[thread overview]
Message-ID: <CAKmKYaAN6sguheaP7qied0KgdDwBxX4H-t+iZgHKBkym-ZuvBw@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_mVUagz2ZTE=D_C4unk34uKqNNJ0AE8LCTXZhDNEOmkBg@mail.gmail.com>

On Fri, Jan 25, 2013 at 12:59 PM, Rich Freeman <rich0@gentoo.org> 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


  reply	other threads:[~2013-01-25 13:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 13:14 [gentoo-dev] news item for udev 197-r3 upgrade (yes, I know, it's late) Samuli Suominen
2013-01-23 13:32 ` Dirkjan Ochtman
2013-01-23 13:34   ` Markos Chandras
2013-01-23 13:41     ` Samuli Suominen
2013-01-23 13:44       ` Rich Freeman
2013-01-23 14:26         ` Samuli Suominen
2013-01-23 14:02 ` Philip Webb
2013-01-23 14:05   ` Diego Elio Pettenò
2013-01-23 15:04     ` Rich Freeman
2013-01-23 15:06       ` Diego Elio Pettenò
2013-01-23 16:03       ` Michael Weber
2013-01-23 21:49         ` Christopher Head
2013-01-24  1:45           ` [gentoo-dev] " »Q«
2013-01-24 14:52             ` Michael Weber
2013-01-23 18:29 ` [gentoo-dev] " Felix Kuperjans
2013-01-23 18:42   ` Mike Gilbert
2013-01-23 18:52     ` Rich Freeman
2013-01-23 18:56       ` Mike Gilbert
2013-01-23 19:09         ` Rich Freeman
2013-01-23 19:06     ` Felix Kuperjans
2013-01-24  2:04       ` Samuli Suominen
2013-01-24  3:11         ` [gentoo-dev] " Duncan
2013-01-24  4:28           ` Dale
2013-01-28  4:45       ` [gentoo-dev] " William Hubbs
2013-01-24 10:02   ` Michael Haubenwallner
2013-01-24 11:40     ` Rich Freeman
2013-01-24 15:49     ` Michael Orlitzky
2013-01-24 19:19       ` Michael Haubenwallner
2013-01-24 20:10         ` Diego Elio Pettenò
2013-01-23 21:21 ` Pacho Ramos
2013-01-23 21:45   ` Samuli Suominen
2013-01-23 22:21     ` Pacho Ramos
2013-01-23 23:07       ` Francesco Riosa
2013-01-24 15:40       ` Ian Stakenvicius
2013-01-25  9:19 ` Dirkjan Ochtman
2013-01-25 11:59   ` Rich Freeman
2013-01-25 13:43     ` Dirkjan Ochtman [this message]
2013-01-25 14:17   ` Ian Stakenvicius
2013-01-25 14:23     ` Dirkjan Ochtman
2013-01-25 14:26       ` Diego Elio Pettenò

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=CAKmKYaAN6sguheaP7qied0KgdDwBxX4H-t+iZgHKBkym-ZuvBw@mail.gmail.com \
    --to=djc@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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