From: Lars Marowsky-Bree <lmb@suse.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [Pacemaker] Linux Plumbers Conference mini-conf on clustering?
Date: Wed, 19 Aug 2009 09:59:43 +0200 [thread overview]
Message-ID: <20090819075943.GF23088@suse.de> (raw)
In-Reply-To: <4A8BAFDD.9070702@linbit.com>
On 2009-08-19T09:55:09, Florian Haas <florian.haas@linbit.com> wrote:
> Lars,
>
> any update on whatever became of this proposal? Phil and myself are
> attending LPC next month -- who else is planning to attend?
Because it was originally in conflict with Linux-Kongress (which would
have been in my home town), I had to cancel my LPC plans. Now L-K has
moved, but that was too late for me to make it to LPC. Ah, well.
Enjoy!
Regards,
Lars
--
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N?rnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
next prev parent reply other threads:[~2009-08-19 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090413225353.GF6147@suse.de>
2009-08-19 7:55 ` [Cluster-devel] Re: [Pacemaker] Linux Plumbers Conference mini-conf on clustering? Florian Haas
2009-08-19 7:59 ` Lars Marowsky-Bree [this message]
2009-08-19 8:19 ` Coly Li
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=20090819075943.GF23088@suse.de \
--to=lmb@suse.de \
/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).