From: rohara@sourceware.org <rohara@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/fence/man Makefile
Date: 15 Jan 2007 20:06:30 -0000 [thread overview]
Message-ID: <20070115200630.12097.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: rohara at sourceware.org 2007-01-15 20:06:30
Modified files:
fence/man : Makefile
Log message:
Include fence_scsi in Makefile.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/fence/man/Makefile.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.10&r2=1.10.2.1
--- cluster/fence/man/Makefile 2006/10/05 16:11:36 1.10
+++ cluster/fence/man/Makefile 2007/01/15 20:06:30 1.10.2.1
@@ -26,6 +26,7 @@
fence_node.8 \
fence_rib.8 \
fence_sanbox2.8 \
+ fence_scsi.8 \
fence_tool.8 \
fence_vixel.8 \
fence_wti.8 \
next reply other threads:[~2007-01-15 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 20:06 rohara [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-16 18:23 [Cluster-devel] cluster/fence/man Makefile rohara
2007-01-15 20:05 rohara
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=20070115200630.12097.qmail@sourceware.org \
--to=rohara@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).