On Thu, 2012-10-18 at 22:14 +0200, Andreas Tille wrote: > I also know that some Git addictives are involved in Blends > anyway and so I consider switching the Blends repository from SVN to > Git.
YES!!! > The first question would be for sure: Would this cause any drastical > harm to anybodies working habits? NO!!! :-) In fact, you can use git pretty much the same way you use svn if so you wish. If you push (a mirror of) your repository to github, even, you can *actually* use the svn client to check it out and commit. I've even heard of some open source solutions for bidirectional git <-> svn mirroring, but apparently at this point they are all not feature complete and very hard to set up. > I could imagine any problems for the actual tasks files of the > different Blends which are maintained by several different people - so > pushing a new workflow on several people might be unacceptable in some > few cases. What I learned from migrating RepoForge svn to git is that it's not as terrifying as it looks like, unless you have some really stubborn people on board that discard anything that sounds like a rational argument. We don't have any such people, so the key to success was good planning and communication: a) Do the best to end up with nice history after conversion b) Explain in details how to continue with traditional workflows c) Be ready for some patient hand-holding of the team members Overall it went very smoothly: even those who were not ecstatic about git in the first place, just mapped this new tool into their old workflow that they find to be convenient and got over it. -- Sincerely yours, Yury V. Zaytsev -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/1350593075.2706.24.camel@newpride
