From: Alex Elder <elder@inktank.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: [PATCH REPOST 0/2] rbd: standardize some variable names
Date: Thu, 03 Jan 2013 16:37:54 -0600 [thread overview]
Message-ID: <50E60842.2040204@inktank.com> (raw)
This series just makes the names of variables for
certain objects follow a consistent naming convention.
-Alex
[PATCH REPOST 1/2] rbd: standardize rbd_request variable names
[PATCH REPOST 2/2] rbd: standardize ceph_osd_request variable names
next reply other threads:[~2013-01-03 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 22:37 Alex Elder [this message]
2013-01-03 22:38 ` [PATCH REPOST 1/2] rbd: standardize rbd_request variable names Alex Elder
2013-01-03 23:06 ` Dan Mick
2013-01-03 22:40 ` [PATCH REPOST 2/2] rbd: standardize ceph_osd_request " Alex Elder
2013-01-03 23:06 ` Dan Mick
2013-01-16 1:38 ` [PATCH REPOST 0/2] rbd: standardize some " Josh Durgin
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=50E60842.2040204@inktank.com \
--to=elder@inktank.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox