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
On 6 aug. 2014, at 15:06, Rohit Yadav rohit.ya...@shapeblue.com 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
Hey,
On 06-Aug-2014, at 3:10 pm, Hugo Trippaers h...@trippaers.nl wrote:
On 6 aug. 2014, at 15:06, Rohit Yadav rohit.ya...@shapeblue.com 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/“
On 6 aug. 2014, at 15:15, Rohit Yadav rohit.ya...@shapeblue.com wrote:
Hey,
On 06-Aug-2014, at 3:10 pm, Hugo Trippaers h...@trippaers.nl wrote:
On 6 aug. 2014, at 15:06, Rohit Yadav rohit.ya...@shapeblue.com wrote:
Hi Hugo,
+1
On a totally different issue, if we’re going to
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 daan.hoogl...@gmail.com
wrote:
Let's consider gitflow and the number of prefixes it suppprts.
biligual
