In our previous episode, Santiago A. said: > Workflows are designed according with the tools you had when you > designed it. Sometimes you improve your workflow as you improve your > knowledge of tools. And sometimes you create new tools to improve your > workflow. > > But sometimes other people create a new tools that improves the system > but requires a dramatic change of workflow for better. I know Changing > of mindset is never easy, but the attitude of "I won't change my > workflow" closes the doors to any improvement. > > Many projects are using Git, we are not talking about early adopters or > isnewisbetter guys. It has been tested in real world for several year, > and may projects are moving to it. So I would give it a second chance. > I'm doing so, in spite I'm not exactly a young boy and early adopter, I > can see some advantages in git easy branching and merging. > > Evaluate git and workflows again as for the first time, as if it were > the first time you have heard about it. Forget Graeme Geldenhuys, > sometimes he says things with manners that.... well, sometimes is looks > like seducing people is not among his virtues but the other way around > ;-), Take a new fresh look to Git.
I've done so every time the discussion looks up. I also have some DVCS experience with Mercurial, and I still don't see it. _______________________________________________ fpc-other maillist - fpc-other@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-other