Re: branch hotfix/coverity-fixes

2014-08-06 Thread Rajani Karuturi
actually, I was planning to delete this branch after the fix passes build and is committed to master. it has 3 or 4 coverity fixes in it. On Wed, Aug 6, 2014 at 6:52 PM, Daan Hoogland wrote: > Let's consider gitflow and the number of prefixes it suppprts. > > biligual spelling checker used.read

Re: branch hotfix/coverity-fixes

2014-08-06 Thread Daan Hoogland
Let's consider gitflow and the number of prefixes it suppprts. biligual spelling checker used.read at your own risk Op 6 aug. 2014 15:18 schreef "Hugo Trippaers" : > > On 6 aug. 2014, at 15:15, Rohit Yadav wrote: > > > Hey, > > > > On 06-Aug-2014, at 3:10 pm, Hugo Trippaers wrote: > > > >> > >>

Re: branch hotfix/coverity-fixes

2014-08-06 Thread Hugo Trippaers
On 6 aug. 2014, at 15:15, Rohit Yadav wrote: > Hey, > > On 06-Aug-2014, at 3:10 pm, Hugo Trippaers wrote: > >> >> On 6 aug. 2014, at 15:06, Rohit Yadav wrote: >> >>> Hi Hugo, >>> >>> +1 >>> >>> On a totally different issue, if we’re going to adopt git-flow let’s not >>> use bug fix bran

Re: branch hotfix/coverity-fixes

2014-08-06 Thread Rohit Yadav
Hey, On 06-Aug-2014, at 3:10 pm, Hugo Trippaers wrote: > > On 6 aug. 2014, at 15:06, Rohit Yadav wrote: > >> Hi Hugo, >> >> +1 >> >> On a totally different issue, if we’re going to adopt git-flow let’s not use >> bug fix branch names with the prefix “hotfix/“ because as the per convention >>

Re: branch hotfix/coverity-fixes

2014-08-06 Thread Hugo Trippaers
On 6 aug. 2014, at 15:06, Rohit Yadav wrote: > Hi Hugo, > > +1 > > On a totally different issue, if we’re going to adopt git-flow let’s not use > bug fix branch names with the prefix “hotfix/“ because as the per convention > it’s for already released versions and for serious production issue

Re: branch hotfix/coverity-fixes

2014-08-06 Thread Rohit Yadav
Hi Hugo, +1 On a totally different issue, if we’re going to adopt git-flow let’s not use bug fix branch names with the prefix “hotfix/“ because as the per convention it’s for already released versions and for serious production issues. Instead, I recommend that we can either go with “feature/C

branch hotfix/coverity-fixes

2014-08-06 Thread Hugo Trippaers
Heya, How about we name the branches for coverity fixes after the relevant CID? Something like /hotfix/CID-xx. That would make it very easy for everyone to track which coverity fixes are tracked where and who is working on which CID. The name hotfix coverity fix is a bit too generic and w