public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: mgrac@sourceware.org To: cluster-cvs@sources.redhat.com, cluster-devel@redhat.com Subject: Cluster Project branch, RHEL47, updated. gfs-kernel_2_6_9_76-66-gda24f0a Date: Mon, 02 Jun 2008 15:21:00 -0000 [thread overview] Message-ID: <20080602152108.11706.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Cluster Project". http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=da24f0a30cb5b9950061cf1502adf263b7e3f68b The branch, RHEL47 has been updated via da24f0a30cb5b9950061cf1502adf263b7e3f68b (commit) from 7e3ccc62b73056a16057d5dc81b8458447007b52 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit da24f0a30cb5b9950061cf1502adf263b7e3f68b Author: Marek 'marx' Grac <mgrac@redhat.com> Date: Mon Jun 2 16:15:50 2008 +0200 [FENCE] Fix #446995: Unknown option Previous patch worked just for command line and there was a problem with stdin argument. Typo fixed. ----------------------------------------------------------------------- Summary of changes: fence/agents/lib/fencing.py.py | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/fence/agents/lib/fencing.py.py b/fence/agents/lib/fencing.py.py index d8b2c4e..b58d9d8 100644 --- a/fence/agents/lib/fencing.py.py +++ b/fence/agents/lib/fencing.py.py @@ -107,7 +107,7 @@ all_opt = { "help" : "-n <id> Physical plug number on device", "order" : 1 }, "switch" : { - "getopt" : "-s:", + "getopt" : "s:", "help" : "-s <id> Physical switch number on device", "order" : 1 }, "test" : { hooks/post-receive -- Cluster Project
reply other threads:[~2008-06-02 15:21 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=20080602152108.11706.qmail@sourceware.org \ --to=mgrac@sourceware.org \ --cc=cluster-cvs@sources.redhat.com \ --cc=cluster-devel@redhat.com \ /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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).