public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: "Christine Caulfield" <ccaulfie@redhat.com> To: cluster-cvs@sources.redhat.com Subject: [SCM] Cluster Project branch, master, updated. gfs-kernel_0_1_22-39-gc9ce321 Date: Wed, 27 Feb 2008 14:43:00 -0000 [thread overview] Message-ID: <20080227144337.23137.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=c9ce3211322e9d3dff1ef454483283042f529a2d The branch, master has been updated via c9ce3211322e9d3dff1ef454483283042f529a2d (commit) from 4d94315324f3a39f47eafd2d2f575360d624cfc1 (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 c9ce3211322e9d3dff1ef454483283042f529a2d Author: Christine Caulfield <ccaulfie@redhat.com> Date: Wed Feb 27 11:16:34 2008 +0000 [CMAN] Don't ignore cman_tool version the processing of the 'cman_tool version' command updates the config_version variable immediately rather than waiting for the message to come back. Because of this, when the message /does/ come back it gets ignored because cman thinks it already has the latest config! The solution is, of course, not to update the config version until we receive the RECONFIGURE message. Signed-off-by: Christine Caulfield <ccaulfie@redhat.com> ----------------------------------------------------------------------- Summary of changes: cman/daemon/commands.c | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) hooks/post-receive -- Cluster Project
reply other threads:[~2008-02-27 14:43 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=20080227144337.23137.qmail@sourceware.org \ --to=ccaulfie@redhat.com \ --cc=cluster-cvs@sources.redhat.com \ /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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).