I found nice comparison of GIT and SVN: http://git.or.cz/gitwiki/GitSvnComparsion
several points are a little crappy and not a TRUE in several cases... Especially everything that touches performance. let's check every argument from that list and write it pluses and minuses: 1) Distributed Nature Pluses/Minuses: in most cases 99% of developers do not need that. They simply want access to the latest sources of the OS. Google keeps server with source code and it's no need in distributed repositiories. 2) Access Control they are mostly equal on GIT and SVN. 3) Branch Handling Pluses/Minuses: merging of branches never will be a simple operation. It can have conflicts that only human can solve. And here is Plus to SVN which have very good GUI for conflicts solving. 3rd party tools also solve this issue for GIT. So no pluses for any one they are equal. Article is old enough in describing SVN functionality - most of that problems was fixed in 1.6 releases. 4) Performance Pluses/Minuses: GIT can do all locally, but at the same time have disadvantage in initialization. You have to clone repository till you can do something with it... SVN is much faster in initialization - you can take one file or required folder only... 5) Small Space Requirements Not actual for today. Disk space cost very low. etc... 90) GUI. Subversion has better GUI. 91) Community support. Subversion has better community support and greater number of users. 92) OSs support. Subversion works perfectly everywhere. GIT has big problems under Windows OS. 93) Distribution. Subversion easily to download and install for any OS. GIT has great number of limitation in that. Download sources, compile them and etc... What for?! I need only binaries for my desktop... 94) Web support. Subversion has great number of web interfaces and additional tools. GIT has only several. And take a look into google gitweb more then 100+ commits in MERGED list touches gitWEB interface. Much better to use man power of that man on other tasks. SVN web interfaces can provide: RSS/Atom, night builds, trackballs, bug tracking, code reviews, code analysis, blaming and etc. the total score of both systems are mostly equal. Only at the part of human interface GIT loose own points greatly. Take a look into GitWeb near 20-40 people only working with Android... with Subversion that can do much more developers. On Apr 30, 4:41 pm, lbcoder <[email protected]> wrote: > Your first suggestion is pointless. GUI is irrelevant. Learn to use > the application as it is intended. > > Your second suggestion is also pointless. Windoze has no place in > Linux development. > > On Apr 30, 8:58 am, AlexK <[email protected]> wrote: > > > > > Hi, > > > I work with Android more then 1 year and found several issues that > > will be good to change. > > > As one person I can not influence on Google Android Team that is why > > I'm asking everyone about taking part in my petitions. > > Android Community have successful petition before - result of which is > > presence on "developer phone" for Android Community. > > > My reasons are simple: I trust in Android, I like it and I want to > > make it better. So please spent 2 minutes of your time and sign > > petitions if you found them close to your hart. > > > ========= PETITION #1 ========= > > Change Android hosting from GIT to > > Subversion:http://www.ipetitions.com/petition/android-svn/ > > > Reasons are: > > - Subversion is also Free and Open Source; > > - Subversion has much better and usable GUI for all OSs; > > - Subversion supports all features required for proper version > > controlling and collaboration of large teams; > > - Subversion has integration with all IDEs that can be used for > > development of Android applications/modules; > > - Subversion has many web UIs for code reviewing, tracking changes, > > bug tracking, etc. And they are more advanced comparing to GitWeb > > solution; > > > ========= PETITION #2 ========= > > Please provide proper support for Windows > > OS:http://www.ipetitions.com/petition/android-win/ > > > Reasons are: > > - Linux and MacOS only two major platforms and ignoring of the third > > major platform - Windows, is a big mistake on my mind; > > - Windows developers also wants to take great part in developing of > > Android internals; providing Android build support only for Linux and > > MacOS only makes "curve" of involvement into Android development very > > low; > > - Windows support will increase community size greatly; > > > more details about supported platforms can be extracted > > fromhttp://source.android.com/download > > > Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
