From: Christine Caulfield <ccaulfie@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Status
Date: Mon, 10 Aug 2009 10:04:49 +0100 [thread overview]
Message-ID: <4A7FE2B1.7040309@redhat.com> (raw)
W/C 3rd August
Monday:
- A bit of SELinux testing
- Looking into why corosync loops when cman does a config reload
develop & test patch. Posted to mailing-list
Tuesday:
- stable3 testing and checking mainly.
- A bit of SELinux pingponging too.
- Checking Bugzillas and patches
Wednesday:
- Trying to reproduce some odd behaviour fabio reported
- Tidied shutdown code in stable3 to remove some duplicates
- Worried that clvmd seems to be not working.
Investigate & fix
Thursday:
- Looking through dlm code to see if I can spot the connect loop
- stable3 & clvmd testing
- Ordering a new headset to replace the one that broke.
Friday:
- Can't remember. sorry. it was important, I'm sure.
next reply other threads:[~2009-08-10 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 9:04 Christine Caulfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-01 6:57 [Cluster-devel] Status Christine Caulfield
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=4A7FE2B1.7040309@redhat.com \
--to=ccaulfie@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 NNTP newsgroup(s).