From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev - drop all methods :)
Date: Mon, 12 Jan 2004 23:53:26 +0000 [thread overview]
Message-ID: <20040112235326.GA9466@vrfy.org> (raw)
In-Reply-To: <20040110181507.GA3969@vrfy.org>
On Mon, Jan 12, 2004 at 03:42:36PM -0800, Greg KH wrote:
> On Sun, Jan 11, 2004 at 11:56:55PM +0100, Kay Sievers wrote:
> > On Sat, Jan 10, 2004 at 07:15:07PM +0100, Kay Sievers wrote:
> >
> > Here is a slightly better version of the patch.
> > After a conversation with Patrick, we are now able to execute the PROGRAM
> > and also match in all following rules with the RESULT value from this exec.
>
> Thanks a lot. I've applied this patch. I also made a few tweaks to the
> parsing logic to help catch old rules files properly (otherwise we end
> up creating rules that the user might not have wanted.) I also cleaned
> up the other test scripts and the config files.
>
> Care to update the documentation so we can make a release for others to
> play with?
Yes, I'll update the man page in the next two hours :)
Kay
-------------------------------------------------------
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-12 23:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 18:15 [PATCH] udev - drop all methods :) Kay Sievers
2004-01-11 22:56 ` Kay Sievers
2004-01-12 23:42 ` Greg KH
2004-01-12 23:53 ` Kay Sievers [this message]
2004-01-13 16:01 ` Patrick Mansfield
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=20040112235326.GA9466@vrfy.org \
--to=kay.sievers@vrfy.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.