From: Alex Elder <elder@dreamhost.com>
To: ceph-devel@vger.kernel.org
Subject: Patch Bomb!
Date: Tue, 28 Feb 2012 18:14:08 -0800 [thread overview]
Message-ID: <4F4D89F0.7000107@dreamhost.com> (raw)
Over the next few hours I plan to send out a lot of patches
for review. Most of these have been around and under test
for a month or more, and at the time I originally committed
them I wasn't sure how best to get them reviewed.
We decided that sending them all out to the list was a
good way to ensure visibility and preserve community
input. So here goes. From now on I'll send patch series
out to the list when they're ready rather than hanging on
to them like this.
-Alex
next reply other threads:[~2012-02-29 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 2:14 Alex Elder [this message]
2012-02-29 3:05 ` Patch Bomb! Alex Elder
2012-02-29 4:59 ` Alex Elder
2012-03-01 3:24 ` Alex Elder
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=4F4D89F0.7000107@dreamhost.com \
--to=elder@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
/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.