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 05:21:47 +0000 [thread overview]
Message-ID: <87br7za32s.fsf@orcus.priv.at> (raw)
In-Reply-To: <20040913121844.GA6208@wonderland.linux.it>
Kay Sievers <kay.sievers@vrfy.org> writes:
>> A more regular syntax would be (for example):
>>
>> %c whole string returned from program
>
> It is that way.
>
>> %3c third word returned from program
>
> This is the length parameter which limit the output to 3 chars.
I did not know that, I couldn't find detailed documentation about the
% escapes.
> I don't understand anything else in this mail, especially not the the
> relation with the mail Subject. What is the problem here?
I'm sorry it was noted in the bugtracking system that this feature
request was already forwarded to the hotplug list, so I thought you
know about this issue. See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug&1181
for the whole thing. I think the original request can't be fulfilled
sensibly...
--
Robbe
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
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:[~2005-04-28 5:21 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 [this message]
2005-04-28 6:06 ` Greg KH
2005-04-28 17:26 ` Robert Bihlmeyer
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=87br7za32s.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).