From: Matthew Kent <matt@bravenet.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] lib/fencing.py long options patch
Date: Fri, 16 Jan 2009 11:54:14 -0800 [thread overview]
Message-ID: <1232135654.24903.82.camel@fuego> (raw)
Recently added long options don't seem to be quite working. Patch
against fencing/master branch included.
--
Matthew Kent \ SA \ bravenet.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fencing-python-longopts.patch
Type: text/x-patch
Size: 537 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20090116/819e12ed/attachment.bin>
reply other threads:[~2009-01-16 19:54 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=1232135654.24903.82.camel@fuego \
--to=matt@bravenet.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: 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).