From: Nathan Cutler <ncutler@suse.cz>
To: Willem Jan Withagen <wjw@digiware.nl>, Ken Dreyer <kdreyer@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: ceph / rocksdb
Date: Mon, 6 Jun 2016 12:43:05 +0200 [thread overview]
Message-ID: <575553B9.8030707@suse.cz> (raw)
In-Reply-To: <9a087a20-84bf-dfdb-876d-0c0c4dec1123@digiware.nl>
> I know that this discussion has run for some time.
> And when I build a fresh clone, I ended up with a more recent rocksdb
> than that I'd liked.... (or actual Clang)
>
> But 3 trivial fixes further I could again compile, so I've committed
> those to the Rocksdb github, and they got accepted this morning.
> Now the trick question here is:
> How do they end up in the src/rocksdb tree?
>
Since rocksdb is built from a git submodule, the answer lies in
https://github.com/ceph/ceph/blob/master/.gitmodules#L15-L18
Which to me looks like it just takes the latest upstream rocksdb (branch
defaults to "master").
Nathan
next prev parent reply other threads:[~2016-06-06 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 6:05 ceph / rocksdb Marcus Watts
2016-02-24 17:58 ` Ken Dreyer
2016-02-24 18:04 ` Allen Samuels
2016-02-24 18:06 ` Sage Weil
2016-02-25 8:15 ` Marcus Watts
2016-02-25 20:21 ` Nathan Cutler
2016-06-06 10:05 ` Willem Jan Withagen
2016-06-06 10:43 ` Nathan Cutler [this message]
2016-06-06 12:26 ` Sage Weil
2016-06-06 12:29 ` Willem Jan Withagen
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=575553B9.8030707@suse.cz \
--to=ncutler@suse.cz \
--cc=ceph-devel@vger.kernel.org \
--cc=kdreyer@redhat.com \
--cc=wjw@digiware.nl \
/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