From: Scott James Remnant <scott@canonical.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 131 release
Date: Fri, 07 Nov 2008 12:59:18 +0000 [thread overview]
Message-ID: <1226062758.2222.4.camel@quest> (raw)
In-Reply-To: <1226039269.4100.0.camel@nga>
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
0On Fri, 2008-11-07 at 10:39 +0100, Marco d'Itri wrote:
> On Nov 07, Kay Sievers <kay.sievers@vrfy.org> wrote:
>
> > The NAME assignment is no longer special cased. If later rules assign
> > a NAME value again, the former value will be overwritten. As usual
> > for most other keys, the NAME value can be protected by doing a final
> > assignment with NAME:="<value>".
> While I like the consistency, I see the potential for user and
> package-specific rules to break spectacularly...
>
In theory, the changes are largely backwards compatible.
I've already grepped through the Ubuntu source, and didn't find anything
relying on the old behaviour.
In fact, I found a few things that will only work with the *new*
behaviour ;)
Scott
--
Scott James Remnant
scott@canonical.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-11-07 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 6:27 [ANNOUNCE] udev 131 release Kay Sievers
2008-11-07 9:39 ` Marco d'Itri
2008-11-07 12:59 ` Scott James Remnant [this message]
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=1226062758.2222.4.camel@quest \
--to=scott@canonical.com \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).