From: ccaulfield@sourceware.org <ccaulfield@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, master, updated. gfs-kernel_0_1_22-176-g4b3ad9a
Date: 16 Apr 2008 12:12:40 -0000 [thread overview]
Message-ID: <20080416121240.23057.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=4b3ad9a381bdb07f0fe8afd58fdaff39a586095f
The branch, master has been updated
via 4b3ad9a381bdb07f0fe8afd58fdaff39a586095f (commit)
from 2bc77b7c45e9d74eb245a10f454e3041f61a1e7f (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 4b3ad9a381bdb07f0fe8afd58fdaff39a586095f
Author: Christine Caulfield <ccaulfie@redhat.com>
Date: Wed Apr 16 13:12:10 2008 +0100
[FENCE] Make it build with gcc 4.3
fence_tool.c also needs <limits.h>
Signed-off-by: Christine Caulfield <ccaulfie@redhat.com>
-----------------------------------------------------------------------
Summary of changes:
fence/fence_tool/fence_tool.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/fence/fence_tool/fence_tool.c b/fence/fence_tool/fence_tool.c
index ab737e5..2d193ea 100644
--- a/fence/fence_tool/fence_tool.c
+++ b/fence/fence_tool/fence_tool.c
@@ -24,6 +24,7 @@
#include <sys/socket.h>
#include <sys/un.h>
#include <fcntl.h>
+#include <limits.h>
#include <errno.h>
#include <libgen.h>
hooks/post-receive
--
Cluster Project
reply other threads:[~2008-04-16 12:12 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=20080416121240.23057.qmail@sourceware.org \
--to=ccaulfield@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.