From: Christophe Saout <christophe@saout.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: IGNORE method
Date: Sat, 10 Jan 2004 10:44:10 +0000 [thread overview]
Message-ID: <1073731450.6584.3.camel@leto.cs.pocnet.net> (raw)
In-Reply-To: <20040110013128.GA2112@vrfy.org>
Am Sa, den 10.01.2004 schrieb Greg KH um 02:35:
> On Sat, Jan 10, 2004 at 02:31:28AM +0100, Kay Sievers wrote:
> >
> > http://linuxusb.bkbits.net:8080/udev/cset@1.395?nav=index.html|ChangeSet@-2d
> >
> > We have a IGNORE rule now?
>
> Yeah, Christophe sent me a patch for one.
>
> > I would prefer a change that simply allows NAME="".
> > That works with every other method, not only kernel names and is much
> > much simpler.
>
> Ah. Yeah, that might be a lot simpler. Something like (in your new
> syntax):
> KERNEL="dm-[0-9]*", NAME=""
>
> It's not the most intuitive, but I could live with it. Christophe, what
> do you think?
Sure, I thought of this too. I added the IGNORE rule because it's more
intuitive but if this is more flexible, I'm ok with it. You should be
aware that this would also ignore an additional SYMLINK.
Should I update my patch or add one on top of it that drops the new
rule?
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-01-10 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 1:31 IGNORE method Kay Sievers
2004-01-10 1:35 ` Greg KH
2004-01-10 10:44 ` Christophe Saout [this message]
2004-01-13 18:08 ` Greg KH
2004-01-13 18:24 ` Christophe Saout
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=1073731450.6584.3.camel@leto.cs.pocnet.net \
--to=christophe@saout.de \
--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).