From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Update writing udev rules documentation
Date: Sat, 03 Jun 2006 16:09:02 +0000 [thread overview]
Message-ID: <200606032009.09065.arvidjaar@mail.ru> (raw)
In-Reply-To: <4481B0C5.80301@gentoo.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 663 bytes --]
On Saturday 03 June 2006 19:54, Daniel Drake wrote:
> Hi,
>
> I finally got around to reworking the udev rules documentation. It is
> now more of a general guide to rule writing and the various things you
> can do, with examples.
>
> The patch isn't very readable, if anyone wants to review the changes I
> suggest you just look at the online version as almost all of it has been
> rewritten:
> http://www.reactivated.net/writing_udev_rules.html
>
> Comments appreciated.
>
> Daniel
there is something wrong with spacing in one place (see screenshot). Also font
in contents looks too big to my taste but it is subjective of course.
-andrey
[-- Attachment #1.1.2: udev-rules.png --]
[-- Type: image/png, Size: 74930 bytes --]
[-- Attachment #1.2: Type: application/pgp-signature, Size: 191 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 226 bytes --]
_______________________________________________
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:[~2006-06-03 16:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-03 15:54 [PATCH] Update writing udev rules documentation Daniel Drake
2006-06-03 16:09 ` Andrey Borzenkov [this message]
2006-06-03 16:40 ` Daniel Drake
2006-06-03 23:38 ` Nick
2006-06-04 10:57 ` Remco
2006-06-04 16:24 ` Remco
2006-06-05 1:15 ` MUNEDA Takahiro
2006-06-06 12:24 ` Bryan Kadzban
2006-06-06 16:19 ` Kay Sievers
2006-06-09 21:52 ` Daniel Drake
2006-06-09 21:58 ` Daniel Drake
2006-06-09 22:34 ` Kay Sievers
2006-07-10 1:37 ` sean
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=200606032009.09065.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--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.