From: fabbione@sourceware.org <fabbione@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, master, updated. cluster-2.99.01-14-g5cc39fb
Date: 19 May 2008 03:57:19 -0000 [thread overview]
Message-ID: <20080519035719.30963.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=5cc39fb3272c6ef46049c834ae0e51d2db844307
The branch, master has been updated
via 5cc39fb3272c6ef46049c834ae0e51d2db844307 (commit)
from 9b7834238366e6dc27143b424d8d8418789beee1 (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 5cc39fb3272c6ef46049c834ae0e51d2db844307
Author: Fabio M. Di Nitto <fdinitto@redhat.com>
Date: Mon May 19 05:57:01 2008 +0200
[GFS] Fix comment
Signed-off-by: Fabio M. Di Nitto <fdinitto@redhat.com>
-----------------------------------------------------------------------
Summary of changes:
gfs-kernel/src/gfs/ops_super.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/gfs-kernel/src/gfs/ops_super.c b/gfs-kernel/src/gfs/ops_super.c
index cfc8faf..4dda387 100644
--- a/gfs-kernel/src/gfs/ops_super.c
+++ b/gfs-kernel/src/gfs/ops_super.c
@@ -62,7 +62,7 @@ gfs_write_inode(struct inode *inode, int sync)
}
/**
- * gfs_drop_inode - put an inode
+ * gfs_drop_inode - drop an inode
* @inode: The inode
*
* If i_nlink is zero, any dirty data for the inode is thrown away.
hooks/post-receive
--
Cluster Project
reply other threads:[~2008-05-19 3:57 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=20080519035719.30963.qmail@sourceware.org \
--to=fabbione@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.