Fair enough. In this case, I was going to push a backport to ceph-ci.git
so that packages would be available when the backport team was ready to
validate it. In other cases, it can be useful to target a PR against a
public branch so that other devs with access can add fixes and continue
testing.
Casey
On 01/03/2017 04:08 PM, Nathan Cutler wrote:
Hi Casey:
Here's what I do, which I think is essentially the same as Sam and Ken
are doing:
git clone https://github.com/smithfarm/ceph
git remote add ceph-ci https://github.com/ceph/ceph
<prepare wip-foo branch>
git push origin wip-foo
<open PR>
git push ceph-ci wip-foo
<wait for http://shaman.ceph.com to build>
<test in Sepia>
HTH,
Nathan
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
