From: "Matt W. Benjamin" <matt@linuxbox.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Cc: Sage Weil <sage@inktank.com>, aemerson <aemerson@linuxbox.com>,
David Zafman <david.zafman@inktank.com>,
Ilya Storozhilov <Ilya_Storozhilov@epam.com>
Subject: wip-libcephfs rebase
Date: Thu, 27 Jun 2013 13:54:29 -0400 (EDT) [thread overview]
Message-ID: <466224703.168.1372355669107.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <260303729.166.1372355254438.JavaMail.root@thunderbeast.private.linuxbox.com>
Hi All,
Just to confirm what Adam and I are doing on this end, ie, this is our plan to rebase wip-libcephfs following wip-libcephfs-rebase.
* proceeding commit-wise on wip-libcephfs-rebase, mapping each change back to a commit in wip-libcephfs
** striking out anything marked reject in rebase
** striking out anything marked "whitespace"
*** (unless you want these)
** either striking out or motivating in commit message anything marked "why"
** updating commit messages of every commit which remains
*** with author, signed off by, SHAs of the source commit(s), updated commit message (background authors)
* test, fix, and rebase as necessary
* cherry-pick changes from Ilya
** adapt anything we propose to adjust in new commits
* rebase on head
* push to our Ceph repo for review/pull when ready
Matt
--
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI 48104
http://linuxbox.com
tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309
next parent reply other threads:[~2013-06-27 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <260303729.166.1372355254438.JavaMail.root@thunderbeast.private.linuxbox.com>
2013-06-27 17:54 ` Matt W. Benjamin [this message]
2013-06-27 19:48 ` wip-libcephfs rebase Sage Weil
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=466224703.168.1372355669107.JavaMail.root@thunderbeast.private.linuxbox.com \
--to=matt@linuxbox.com \
--cc=Ilya_Storozhilov@epam.com \
--cc=aemerson@linuxbox.com \
--cc=ceph-devel@vger.kernel.org \
--cc=david.zafman@inktank.com \
--cc=sage@inktank.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.