From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] udev-021: fix configuration directory parsing
Date: Sat, 13 Mar 2004 19:53:41 +0000 [thread overview]
Message-ID: <200403132253.41698.arvidjaar@mail.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 72 bytes --]
We do not want to force trailing slash on directory name?
-andrey
[-- Attachment #2: udev021_namedev_parse-slash.patch --]
[-- Type: text/x-diff, Size: 448 bytes --]
--- udev-021/namedev_parse.c.slash 2004-03-03 03:01:31.000000000 +0300
+++ udev-021/namedev_parse.c 2004-03-13 22:00:52.491720344 +0300
@@ -423,6 +423,7 @@ static int call_foreach_file(int parser
/* parse every file in the list */
list_for_each_entry_safe(loop_file, tmp_file, &file_list, list) {
strfieldcpy(file, filename);
+ strfieldcat(file, "/");
strfieldcat(file, loop_file->name);
parser(file);
list_del(&loop_file->list);
reply other threads:[~2004-03-13 19:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200403132253.41698.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 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).