----- Original Message ----- > From: "Maru Newby" <[email protected]> > To: "OpenStack Development Mailing List (not for usage questions)" > <[email protected]> > > Am I the only one wondering whether introducing arbitrary tagging into our > commit messages sets a bad precedent? Or was there a discussion on this > topic that I missed? > > Maru
Any particular reason for digging this up from June? We already changed the process so that we did not need to do this. Thanks, Steve > On Jun 17, 2014, at 2:27 PM, Sylvain Bauza <[email protected]> wrote: > > > Hi, > > > > There is an action for creating a Gerrit dashboard to show all > > NFV-related specs and patches. > > As it requires to have a specific label for discriminating them, I'm > > adding "NFVImpact" in all the patches proposed in [1]. > > The side effect is that it creates another patchset and so runs another > > Jenkins check so don't worry about it. > > > > I'll do a team status by tomorrow but meanwhile, please make sure that > > if you upload a new patch to Gerrit, it will be marked as "NFVImpact" in > > the commit message. > > > > Many thanks, > > -Sylvain > > > > > > [1] https://wiki.openstack.org/wiki/Teams/NFV#Active_Blueprints > > > > _______________________________________________ > > OpenStack-dev mailing list > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Steve Gordon, RHCE Sr. Technical Product Manager, Red Hat Enterprise Linux OpenStack Platform _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
