From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: DEVLINKS and DEVNAME variables in RUN rules
Date: Thu, 26 Jan 2006 01:18:50 +0000 [thread overview]
Message-ID: <20060126011850.GA1399@vrfy.org> (raw)
In-Reply-To: <m3bqy1a91w.fsf@dynamo.mandriva.com>
On Wed, Jan 25, 2006 at 10:38:19PM +0300, Andrey Borzenkov wrote:
> On Wednesday 25 January 2006 22:10, Kay Sievers wrote:
> > Hehe, no, as mentioned in the last mail,
>
> too late :)
Yeah, I know that. :)
> > we can't patch the created man
> > page, it comes from "docs/udev.xml".
>
> Why is it verion-controlled then?
It just avoids the dependency on xmlto, no special reason.
> > I don't mind putting it in there myself, but if you want to send a new
> > patch, go for it. :)
>
> third attempt. I do not mind, I practice (st-)git on your expense :) This time
> attached due to overly long lines.
Thanks, I've applied this.
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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
prev parent reply other threads:[~2006-01-26 1:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 16:24 DEVLINKS and DEVNAME variables in RUN rules Olivier Blin
2006-01-24 18:05 ` Andrey Borzenkov
2006-01-24 19:43 ` Kay Sievers
2006-01-25 18:18 ` Andrey Borzenkov
2006-01-25 18:25 ` Olivier Blin
2006-01-25 18:52 ` Kay Sievers
2006-01-25 19:03 ` Andrey Borzenkov
2006-01-25 19:10 ` Kay Sievers
2006-01-25 19:38 ` Andrey Borzenkov
2006-01-26 1:18 ` Kay Sievers [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=20060126011850.GA1399@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 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).