2009/3/16 Youness Alaoui <kakar...@kakaroto.homelinux.net>: > > yes, but the question really is "does git's power warrant > its un-easy-ness"... in other words, all those extra > features, do we *need* them ? I don't feel like we do... > either way, anyone could be using git-svn and have local > branches, etc...
Yep that's the question you have to answer ;) I did use git-svn, but the trouble is that with 10k+ commits it takes a long time to do a checkout because git needs all the history locally (needless to say that a normal git repo doesn't have this problem because it's protocol is thought differently) > oh, you worked on centericq? nice to know! I just realized > we never actually had formal introductions.. :) Yes I was among the developers who decided to fork centericq to centerim and now I am somewhat the mantainer of the 4.x version, even though I don't spend so much time on it... > anyways, yes, you can get used to git, but i've been using > it every day for a year now and I still find it hard to > use.. with svn it's easy.. "svn checkout/update/commit" you > don't really need anything else.. with git, you really need > to know a lot of stuff just to get the basic stuff done... > IT also exposes its internal state to you.. like doing > a commit requiring a 'git add -u' and the reflogs and > stuff.. Well yeah with svn you just have to checkout/update/commit, but you also have less control over your workflow. For instance the fact that you have to git add the things you want to commit allows you to split your work in more detailed commits (i.e. when you worked on 2 features, but forgot to make a commit after the first feature). Also the fact that what your commit is only held locally until you decide it is worth sharing is another thing I really like... But we could go on and on about pros and cons, some people like me prefer control over simplicity, others (like you I guess) prefer the other way around... And either way is fine if the work gets done ;) > Anyways, I think git is for advanced developers, and while > we do have talented developers here who can easily pick up > git, I beleive that there are some people who are not yet > ready for it.. new developers who never used any RCS ever > before, or translators, or users, etc... The learning curving is too steep > and the tool was really done for 'kernel hackers' rather > than mortals like us... Well let's just say that a random user who follows the instructions for using SVN or git (in its simplest form) will more likely understand what goes on with SVN and not with git. Which in turn leads to less probability of making mistakes, so yeah that should be kept in mind too ;) > well, it's really not that bad, it only has one huge > disadvantage, it's the fact that a merge is basically about > applying a huge patch and you loose your commit history > (although you can get it from the log of the other branch), > but apart from that, svn branches still does work nicely. That is a deal breaker for me, I have to be able to use $scm blame without further ado! (It's just that I like to ask when I see something silly because there may be a reason for it after all...) -- Stéphane ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
