From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, STABLE2, updated. cluster-2.03.04-12-g72e56df
Date: 13 Jun 2008 13:50:14 -0000 [thread overview]
Message-ID: <20080613135014.1607.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=72e56df08d77b3ff2bea852dcf66ce7b3eb6171e
The branch, STABLE2 has been updated
via 72e56df08d77b3ff2bea852dcf66ce7b3eb6171e (commit)
from 82c082823e91ad190592cffb7a3dad3f187b3713 (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 72e56df08d77b3ff2bea852dcf66ce7b3eb6171e
Author: Bob Peterson <rpeterso@redhat.com>
Date: Fri Jun 13 08:43:26 2008 -0500
Fix 32-bit warning in super.c.
-----------------------------------------------------------------------
Summary of changes:
gfs/gfs_fsck/super.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/gfs/gfs_fsck/super.c b/gfs/gfs_fsck/super.c
index b18228c..b2c81f1 100644
--- a/gfs/gfs_fsck/super.c
+++ b/gfs/gfs_fsck/super.c
@@ -1160,7 +1160,7 @@ int ri_update(struct fsck_sb *sdp)
free(expected_rgd);
} /* if we can't trust the rg index */
else { /* blind faith -- just check for the gfs_grow problem */
- if (rgd->rd_ri.ri_data == 4294967292) {
+ if (rgd->rd_ri.ri_data == (uint32_t)-4) {
if (!fix_grow_problems) {
log_err("A problem with the rindex file caused by gfs_grow was detected.\n");
if(query(sdp, "Fix the rindex problem? (y/n)"))
hooks/post-receive
--
Cluster Project
reply other threads:[~2008-06-13 13:50 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=20080613135014.1607.qmail@sourceware.org \
--to=rpeterso@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).