All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <jdurgin@redhat.com>
To: Willem Jan Withagen <wjw@digiware.nl>,
	Gregory Farnum <gfarnum@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: getting more updates in rocksdb
Date: Wed, 20 Jul 2016 07:23:40 -0700	[thread overview]
Message-ID: <578F896C.1000501@redhat.com> (raw)
In-Reply-To: <1e5059aa-9470-4edc-6229-4a9346988fb3@digiware.nl>

On 07/20/2016 06:52 AM, Willem Jan Withagen wrote:
> On 20-7-2016 15:32, Gregory Farnum wrote:
>> On Wed, Jul 20, 2016 at 3:38 AM, Willem Jan Withagen <wjw@digiware.nl> wrote:
>>>
>>> Hi,
>>>
>>> I submitted a small patch to rocksdb for FreeBSD
>>> https://github.com/facebook/rocksdb/commit/b726bf59619d43651838e03cce9f876b3560cbda
>>>
>>> And was hopping that it would be tracked by my Ceph stuff as well.
>>> But refetching things, it does not seem to be in the tree ceph cmake
>>> fetches.
>>>
>>> And I'm not fluent enough in git to actually check if my current
>>> checkout with hash: 5647fa427c4eab87c0caf8bcbb91f5846a4623f9
>>> should contain the above commit.
>>
>> Use "git log" on both trees and search for the hashes? :)
>>
>> Anyway, the Ceph submodule does not auto-update (git submodules don't
>> support that AFAIK). You can go into the rocksdb folder and try
>> checking out the latest upstream master, then committing the new hash
>> as a commit in the Ceph git repo (at least, once your commit is
>> merged; not sure if it is yet).
>
> Although I (sort of) understand what you are saying, I'm not able to
> reproduce the actual commands to do this. Comparing the logs I
> understand. First just have to clone rocksdb.
>
> And as far as I know the commit I'm looking for is in the current
> rocksdb tree. I got commit about 22 days ago, and the current hash seems
> te be from just a bit before that.

To clarify, to update the rocksdb submodule, you'd need to first update
the ceph fork. (cat .gitmodules shows src/rocksdb comes from
https://github.com/ceph/rocksdb).

You can make a PR to ceph/rocksdb with the latest upstream code from
within your submodule checkout (src/rocksdb) which functions like a
normal git repo itself. You could e.g. 'git pull 
https://github.com/facebook/rocksdb' to get the latest code there.

Then once that's merged into ceph/rocksdb, make a PR to ceph (from the
root of your ceph checkout 'git commit src/rocksdb' will update the
sha1 the rocksdb submodule references).

Josh


  reply	other threads:[~2016-07-20 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 10:38 getting more updates in rocksdb Willem Jan Withagen
2016-07-20 13:32 ` Gregory Farnum
2016-07-20 13:52   ` Willem Jan Withagen
2016-07-20 14:23     ` Josh Durgin [this message]
2016-07-21  7:15       ` Tone Zhang
2016-07-21  8:15         ` Willem Jan Withagen
2016-07-21  8:59           ` Tone Zhang
2016-07-21  9:16             ` Willem Jan Withagen
2016-07-21  9:37               ` Tone Zhang
2016-07-22 20:05                 ` Dan Mick

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=578F896C.1000501@redhat.com \
    --to=jdurgin@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gfarnum@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 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.