From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============8223384421037194575==" MIME-Version: 1.0 From: Young Tack Jin Subject: Re: [SPDK] git config for spdk/qemu review Date: Fri, 03 May 2019 17:00:28 -0700 Message-ID: In-Reply-To: DA1B28FA-D08B-4537-9DB7-E7B0A8F5D9C9@intel.com List-ID: To: spdk@lists.01.org --===============8223384421037194575== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi Jim, Thanks for your time to merge rockdb commit. I understand all core maintainers are super busy to review the bunch of spdk commits and could miss other repo's commits. I'm seeing merge conflict for spdk/qemu with "git pull --all". But this works fine for spdk/spdk repo. If without --all, git pull for spdk/qemu passed successfully. This is not critical now to work on spdk/qemu repo. I think someone could investigate two repos' setup. Regards, YT -----Original Message----- From: SPDK On Behalf Of Harris, James R Sent: Thursday, May 2, 2019 8:12 PM To: Storage Performance Development Kit Subject: Re: [SPDK] git config for spdk/qemu review Hi YT, Configuration works similarly to spdk/spdk - just replace spdk/spdk with spdk/qemu in your .git/config. You'll also need to replace master with the name of the target QEMU branch. I've just merged your spdk/rocksdb patch now. Apologies for the delay. -Jim =EF=BB=BFOn 5/2/19, 5:26 PM, "SPDK on behalf of Young Tack Jin" wrote: Hi all, Could anyone help with how to configure git for spdk/qemu review? SPDK Development guide works only for spdk/spdk review. And my commit to spdk/rocksdb review has been pending so long. Anyone of spdk core maintainers might resolve where this to go. Thanks, YT _______________________________________________ SPDK mailing list SPDK(a)lists.01.org https://lists.01.org/mailman/listinfo/spdk _______________________________________________ SPDK mailing list SPDK(a)lists.01.org https://lists.01.org/mailman/listinfo/spdk --===============8223384421037194575==--