From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Yet another patch
Date: Tue, 27 Feb 2001 01:36:40 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98323806604610@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98322311529463@msgid-missing>
Thanks, I think I'll be checking this stuff in soon.
I tested it with bash1 and bash2; found a bug
from somewhere for bash1 systems, "unset IFS"
was failing.
Comments should be good in "usb.handmap"
(which will likely collect lots of HID devices
like joysticks and mice) and other places that
users edit by hand.
One thing to watch out for is that this way of
handling comment lines expects BASH to be
able to parse the comments, so this "comment"
# Don't use punctuation.
would cause at least two errors (unterminated
string literal and strange number format).
But it's still better than no comments at all!
- Dave
----- Original Message -----
From: "Gioele Barabucci" <dev@gioelebarabucci.com>
To: <linux-hotplug-devel@lists.sourceforge.net>
Sent: Monday, February 26, 2001 1:58 PM
Subject: Yet another patch
> This patch is like to previous one but adds the ability to use comments in
> *map files, but this this time the lines just have to start with "#" followed
> by any string (in the past patch "##" were not recognized as comment)
>
> the patch is done against CVS at 22:20
>
>
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-02-27 1:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 21:58 Yet another patch Gioele Barabucci
2001-02-27 1:36 ` David Brownell [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=marc-linux-hotplug-98323806604610@msgid-missing \
--to=david-b@pacbell.net \
--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).