Broken is bad. Broken can't be good ;-)
2010/10/29 Michał Piotrowski <[email protected]> > 2010/10/29 Konstantin Kudryashov <[email protected]>: > > But i like to keep my master clean. This allows all Behat users to > securely > > clone/submodule from it, keeping in mind, that it's stable. And if they > want > > latest unstable - they can pull develop branch. And all hot-fixes from > > master gets automerged to develop if you use `git-flow` tool, so you > don't > > miss anything! > > > > It's just another branching model. It's not bad, > > I didn't say it's bad - I said IMHO it's broken :) > > But now I understand that you want to keep master in stable state. > > > Best regards, > Michal > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
