linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: new release of udev?
Date: Mon, 23 May 2005 09:43:21 +0000	[thread overview]
Message-ID: <20050523094321.GA9529@wonderland.linux.it> (raw)
In-Reply-To: <20050519065848.GA25640@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]

On May 22, Kay Sievers <kay.sievers@vrfy.org> wrote:

> Well, I personaly prefer to put _all_ my custom rules in _one_ file.
> Your solution solves only _your_ problem, which _is_ a great argument.
Looks like different people have different problems...

> > The rules.d/ directory file names. For the debian package I'm documenting
> > a policy like "all default permissions are set before 030_*" and "RUN
> > rules must be set from z40_* onward" (the actual values will change).
> > If the order of rules is important, then this needs to be documented to
> > allow users and package maintainers to choose the right file names.
> Well, sounds like a pretty complicated requirement to solve a simple problem.
This is something needed for all proposed schemes, none of them is
order-indepented.

> Anyway, I will do the "final assignments". Just ignore it if you don't
> like it. :)
> I see no problem to clear a value list if "=" is used instead of '+='.
> The parser already supports this, I wanted to do this somtimes anyway.
> 
> I will _not_ add any more OPTIONS for individual keys like the "last_run_rule",
> stuff. That belongs to the key operation itself not in the OPTIONS.
OK. I can live with this just as well as long as you can add support for
+= and the revised =.

-- 
ciao,
Marco

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-05-23  9:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:58 new release of udev? Greg KH
2005-05-19  7:30 ` Kay Sievers
2005-05-19  7:55 ` Greg KH
2005-05-19 10:32 ` Marco d'Itri
2005-05-19 14:12 ` Kay Sievers
2005-05-19 16:09 ` Marco d'Itri
2005-05-19 17:49 ` Darren Salt
2005-05-19 21:02 ` Greg KH
2005-05-19 21:24 ` Darren Salt
2005-05-19 22:31 ` Kay Sievers
2005-05-22  0:59 ` Marco d'Itri
2005-05-22  1:09 ` Kay Sievers
2005-05-22 12:01 ` Marco d'Itri
2005-05-22 12:42 ` Kay Sievers
2005-05-22 12:55 ` Marco d'Itri
2005-05-22 13:00 ` Kay Sievers
2005-05-22 13:07 ` Marco d'Itri
2005-05-22 17:38 ` Kay Sievers
2005-05-23  6:52 ` Hannes Reinecke
2005-05-23  7:34 ` Marco d'Itri
2005-05-23  9:43 ` Marco d'Itri [this message]
2005-06-20 18:10 ` Marco d'Itri
2005-06-20 20:40 ` Kay Sievers

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=20050523094321.GA9529@wonderland.linux.it \
    --to=md@linux.it \
    --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).