given the code size, a BP may be a over stretch. I'd just file a review + bug
-- dims On Fri, Sep 5, 2014 at 1:29 AM, Zang MingJie <zealot0...@gmail.com> wrote: > does it require bp or bug report to submit oslo.concurrency patch ? > > > On Wed, Sep 3, 2014 at 7:15 PM, Davanum Srinivas <dava...@gmail.com> wrote: >> >> Zang MingJie, >> >> Can you please consider submitting a review against oslo.concurrency? >> >> >> http://git.openstack.org/cgit/openstack/oslo.concurrency/tree/oslo/concurrency >> >> That will help everyone who will adopt/use that library. >> >> thanks, >> dims >> >> On Wed, Sep 3, 2014 at 1:45 AM, Zang MingJie <zealot0...@gmail.com> wrote: >> > Hi all: >> > >> > currently oslo provides lock utility, but unlike other languages, it is >> > class lock, which prevent all instances call the function. IMO, oslo >> > should >> > provide an instance lock, only lock current instance to gain better >> > concurrency. >> > >> > I have written a lock in a patch[1], please consider pick it into oslo >> > >> > [1] >> > >> > https://review.openstack.org/#/c/114154/4/neutron/openstack/common/lockutils.py >> > >> > _______________________________________________ >> > OpenStack-dev mailing list >> > OpenStack-dev@lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >> >> >> >> -- >> Davanum Srinivas :: http://davanum.wordpress.com >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Davanum Srinivas :: http://davanum.wordpress.com _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev