> As for the GIt conversion, I don't get it. We're not the Linux kernel. There > aren't zillions of patches pending to be applied every day. In fact, there > are pretty much zero patches. If folks want to make changes, and make a > difference, then make or find an issue on Jira, and submit a patch. There's > nothing in the toolset holding that up. When Ben throws up the white flag > because of the crushing load of source patches coming in to core instead of > just chatter on the ML, then maybe there's motivation to change to something > like Git.
I don't really care what Stripes uses (other than I have a deep dislike and fear of Maven, but I'm not the one who has to live with it ;-), but I think this is a misunderstanding of the power of Git. I don't use Git because I expect a lot of contributions. I use Git for all my own projects because of two reasons: 1) Local commits. You don't need IP connectivity to commit anything. This has the advantage that you can keep the workflow even while traveling or when the internet goes bad. 2) Easy branching and merging. It makes a lot of sense to always start a clean branch *from a stable root* when you're hacking on a feature. You can keep committing, tinker at will, and then finally merge the whole thing at the root, or just throw the branch away. This is especially valuable when multiple people work on the same tree (you get to keep the master stable and new features get merged in when they are stable(ish)), but it works really well when you're developing on your own too. I'm a bit ADHD when it comes to development, and I often try out different things. With SVN you need to keep multiple projects open, with Git you just switch between branches, cherry-pick changes, merge and branch. In fact, whenever a project uses SVN, I just usually check it out as a Git project and use Git locally on it... Git has good SVN support, but a native Git project is always better. Just my 2c. /Janne ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
