From: jparsons@sourceware.org <jparsons@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/fence/agents/wti fence_wti.pl
Date: 16 Aug 2006 19:10:46 -0000 [thread overview]
Message-ID: <20060816191046.14999.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: jparsons at sourceware.org 2006-08-16 19:10:46
Modified files:
fence/agents/wti: fence_wti.pl
Log message:
Ignore unused args to stdin
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/fence/agents/wti/fence_wti.pl.diff?cvsroot=cluster&r1=1.4&r2=1.5
--- cluster/fence/agents/wti/fence_wti.pl 2005/07/08 20:09:56 1.4
+++ cluster/fence/agents/wti/fence_wti.pl 2006/08/16 19:10:46 1.5
@@ -352,9 +352,5 @@
# FIXME should we do more error checking?
# Excess name/vals will be eaten for now
- else
- {
- fail "parse error: unknown option \"$opt\"\n";
- }
}
}
next reply other threads:[~2006-08-16 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 19:10 jparsons [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-31 20:00 [Cluster-devel] cluster/fence/agents/wti fence_wti.pl jparsons
2007-01-31 20:20 jparsons
2007-01-31 20:22 jparsons
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=20060816191046.14999.qmail@sourceware.org \
--to=jparsons@sourceware.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).