[openstack-dev] [OpenStack-dev] How to modify a bug across multiple repo?

Christopher Yeoh cbkyeoh at gmail.com
Tue Dec 3 10:06:00 UTC 2013


Hi,

On Tue, Dec 3, 2013 at 7:21 PM, Robert Collins <robertc at robertcollins.net>wrote:

> No, you need to manually arrange to land your changes in first one
> repo then the other.
>
> -Rob
>
> On 3 December 2013 19:17, wu jiang <wingwj at gmail.com> wrote:
> > Hi all,
> >
> > Recently, I found a bug at API layer in Cinder, but the modifications
> relate
> > to CinderClient & Tempest.
> > So, I'm confused how to commit it. Can 'git --dependence' cross different
> > Repo?
>


Just to expand on what Rob mentioned - for situations like this its pretty
common
not to be able to just say make a change in cinder first because the
tempest test will
fail. And at the same time you can't make the final change in tempest first
because the
cinder change hasn't applied yet. If this is your situation what I'd
suggest you do is:

- Submit the cinder change, it will fail tempest, that's ok, you might want
to leave a comment
saying you are waiting on a tempest change to land first.

- Submit a tempest change which disables the tempest tests which fail
because of your change
and in the commit message reference the gerrit url for the cinder change.
Its very helpful, but not
always necessary if you can get a cinder core to +1 this patch so the
tempest cores know that the
cinder team is happy with what is going on.

- Once the tempest change has merged, the cinder change should be able to
merge.

- Submit a tempest change enabling the disabled test(s) and modifying it
for the expected behaviour.

Yes, it would be nice to be able to have cross project dependent patches :)

Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131203/57906ccb/attachment.html>


More information about the OpenStack-dev mailing list