From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Pushed rgmanager cleanups to lhh_rgmanager_cleanup
Date: Fri, 19 Jun 2009 14:21:12 -0400 [thread overview]
Message-ID: <1245435672.9650.46.camel@ayanami> (raw)
Hi,
I just pushed these for review. The commits include:
* dead code deletion
* depends.c, dtest.c - weren't using them anyway
* some #if 0 blocks (but not all yet)
* compiler warning cleanups
* this required a lot of work including moving prototypes around
and so forth (including new header file creation)
* Made lots of functions use 'const' where they should have been
all along.
I have a few other fixes for S3 that I need to put in, but they
shouldn't touch these fixes.
I'm not aware of any actual bug this cleanup fixes, but no compiler
warnings is nice ;)
-- Lon
reply other threads:[~2009-06-19 18:21 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=1245435672.9650.46.camel@ayanami \
--to=lhh@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 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.