[openstack-dev] [OpenStack-Dev] Cherry picking commit from oslo-incubator

Alex Meade alex.meade at rackspace.com
Thu Jan 16 19:58:21 UTC 2014

I think I agree with you John. Micromanaging the common library just makes more work. Is there any argument to not syncing everything? And do you mean cherry-picking only some of the changes in a single module?!? if that's the case then future syncing could get weird, really weird.


-----Original Message-----
From: "John Griffith" <john.griffith at solidfire.com>
Sent: Thursday, January 16, 2014 2:48pm
To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org>
Subject: [openstack-dev] [OpenStack-Dev] Cherry picking commit from oslo-incubator

Hey Everyone,

A review came up today that cherry-picked a specific commit to OSLO
Incubator, without updating the rest of the files in the module.  I
rejected that patch, because my philosophy has been that when you
update/pull from oslo-incubator it should be done as a full sync of
the entire module, not a cherry pick of the bits and pieces that you
may or may not be interested in.

As it turns out I've received a bit of push back on this, so it seems
maybe I'm being unreasonable, or that I'm mistaken in my understanding
of the process here.  To me it seems like a complete and total waste
to have an oslo-incubator and common libs if you're going to turn
around and just cherry pick changes, but maybe I'm completely out of



OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org

More information about the OpenStack-dev mailing list