From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, STABLE2, updated. cluster-2.03.00-11-gc6bb755
Date: 15 Apr 2008 14:42:13 -0000 [thread overview]
Message-ID: <20080415144213.18137.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=c6bb7557e85b3363ff0fd10f1411373f4b747366
The branch, STABLE2 has been updated
via c6bb7557e85b3363ff0fd10f1411373f4b747366 (commit)
from e1718ace02bf0c3f890676b246816fc184b9d07b (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 c6bb7557e85b3363ff0fd10f1411373f4b747366
Author: Bob Peterson <rpeterso@redhat.com>
Date: Tue Apr 15 09:33:26 2008 -0500
bz438762: gfs_tool: Cannot allocate memory
-----------------------------------------------------------------------
Summary of changes:
gfs/gfs_tool/df.c | 2 +-
gfs/gfs_tool/tune.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/gfs/gfs_tool/df.c b/gfs/gfs_tool/df.c
index 8ddbd04..fcea608 100644
--- a/gfs/gfs_tool/df.c
+++ b/gfs/gfs_tool/df.c
@@ -30,7 +30,7 @@
#include "gfs_tool.h"
-#define SIZE (65536)
+#define SIZE (4096)
/**
* do_df_one - print out information about one filesystem
diff --git a/gfs/gfs_tool/tune.c b/gfs/gfs_tool/tune.c
index 93f35df..581c9eb 100644
--- a/gfs/gfs_tool/tune.c
+++ b/gfs/gfs_tool/tune.c
@@ -29,7 +29,7 @@
#include "gfs_tool.h"
-#define SIZE (65536)
+#define SIZE (4096)
/**
* get_tune - print out the current tuneable parameters for a filesystem
hooks/post-receive
--
Cluster Project
reply other threads:[~2008-04-15 14:42 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=20080415144213.18137.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 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.