public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: fabbione@sourceware.org
To: cluster-cvs@sources.redhat.com, cluster-devel@redhat.com
Subject: Cluster Project annotated tag, cluster-2.03.01, created. cluster-2.03.01
Date: Mon, 21 Apr 2008 19:25:00 -0000	[thread overview]
Message-ID: <20080421192546.2848.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=a4391c7b5c974a9bf1ab5be575e230496535d07d

The annotated tag, cluster-2.03.01 has been created
        at  a4391c7b5c974a9bf1ab5be575e230496535d07d (tag)
   tagging  e80c1ff7cfb63e247a4479c4a20f65d373d99b62 (commit)
  replaces  cluster-2.03.00
 tagged by  Fabio M. Di Nitto
        on  Mon Apr 21 21:22:28 2008 +0200

- Log -----------------------------------------------------------------
cluster-2.03.01 release

Abhijith Das (3):
      gfs2_tool: Fix build warnings in misc.c bz 441636
      gfs2_tool manpage: Updates to the manpage for bz441636
      gfs2_tool: Fix build warnings in misc.c bz 441636

Andrew Price (2):
      [GFS2] gfs2_fsck: Fix operation on 'ptr' may be undefined warnings
      [GFS2] gfs2_edit: Remove duplicate linux_endian.h

Bob Peterson (4):
      bz440896/440897 GFS: gfs_fsck should repair gfs_grow corruption
      bz425421: gfs mount attempt hangs if no more journals available
      bz438762: gfs_tool: Cannot allocate memory
      bz295301: Need man page for gfs_edit

Christine Caulfield (4):
      [CMAN] Save the new expected_votes when a node is removed
      [MISC] Make it build with gcc 4.3
      [FENCE] Make it build with gcc 4.3
      [CMAN] Disallow a new dirty node from joining the cman cluster

David Teigland (2):
      gfs: don't cancel glocks when writing to hidden file
      gfs_controld: retry recovery for withdrawn journal

Fabio M. Di Nitto (6):
      [GFS2] Fix build warning
      [BUILD] Fix typo
      Revert "gfs2_tool: Fix build warnings in misc.c bz 441636"
      [RGMANAGER] Fix build with gcc4.3
      [GFS2] Fix build warning
      [KERNEL] Update modules to build with 2.6.25

Lon Hohberger (2):
      [fence] Fix #441737 - fence_node broken due to internal API change
      Revert "[fence] Fix #441737 - fence_node broken due to internal API change"

jparsons (1):
      Bump MAX_DEVICES in fenced from 4 to 8

-----------------------------------------------------------------------


hooks/post-receive
--
Cluster Project


                 reply	other threads:[~2008-04-21 19:25 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=20080421192546.2848.qmail@sourceware.org \
    --to=fabbione@sourceware.org \
    --cc=cluster-cvs@sources.redhat.com \
    --cc=cluster-devel@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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).