From: Robert Bihlmeyer <robbe@orcus.priv.at>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#261181: udev: doesn't notice parentheses in rules file
Date: Thu, 28 Apr 2005 17:26:04 +0000 [thread overview]
Message-ID: <87oebyn783.fsf@orcus.priv.at> (raw)
In-Reply-To: <20040913121844.GA6208@wonderland.linux.it>
[-- Attachment #1: Type: text/plain, Size: 332 bytes --]
[dropping bugs.debian.org, as we are on a tangent now]
Greg KH <greg@kroah.com> writes:
>> I did not know that, I couldn't find detailed documentation about the
>> % escapes.
>
> Does 'man udev' not provide enough information about these?
In 056 udev(8) tells me that %c exists, but neither about %3c nor
about %c{3}.
--
Robbe
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-28 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 12:18 Bug#261181: udev: doesn't notice parentheses in rules files Marco d'Itri
2005-04-26 5:51 ` Bug#261181: udev: doesn't notice parentheses in rules file Robert Bihlmeyer
2005-04-26 11:30 ` Kay Sievers
2005-04-28 5:21 ` Robert Bihlmeyer
2005-04-28 6:06 ` Greg KH
2005-04-28 17:26 ` Robert Bihlmeyer [this message]
2005-04-28 18:30 ` Kay Sievers
2005-04-29 5:28 ` Robert Bihlmeyer
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=87oebyn783.fsf@orcus.priv.at \
--to=robbe@orcus.priv.at \
--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).