4 ms·
I think you're better off just using Git.
by cookiecaper 17y ago
I think you're better off just using Git.
- devdev 17y agoI think this is mainly aimed at enterprise users where subversion is still very relevant.
- cookiecaper 17y agoThey should use git-svn. It lets you still talk to that ugly SVN server and mostly obscures any associated pain. You just use git like normal, and then when you need to push to the SVN server, it's just git svn dcommit, or git svn rebase to pull. SVN doesn't know any different and you're not stuck trying to deal with it.
- WorkerBee 17y agoThey should use git-svn. using a new version with a few new features of an existing tool (svn) is always an easier sell than using two new tools (git, git-svn) as well, especially when one (git) has a reputation as being very complex, and the other (git-svn) looks like a hack to glue two different systems together.
- cookiecaper 17y agoWell, the thing about git-svn is no one has to know you're using it. The commits look just like they were submitted by SVN. You don't have to sell git or git-svn to anyone. Everyone can keep using SVN, and you can use git, and there would be no issue or problem here at all.
- jrockway 17y agoIt's more fun to spend your free time copying git-svn's features and implementing them in Subversion. Or something. Personally, I would find it more useful to sit around and watch paint peel off my wall. But then again, I didn't write a book about why open source projects should have 100-message-long votes on every line of code to be added to the project... so I clearly don't "get it".
- WorkerBee 17y agoIt's more fun to spend your free time copying git-svn's features and implementing them in Subversion. Or something. For most of us, no. For the SVN team, other forces are at work - I'd say familiarity of the code and desire for their baby to stay relevant are big ones.
- WorkerBee 17y agoYou don't have to sell git or git-svn to anyone. It has to be sold to me (or your typical departmental svn user). I do spend time learning new tools, but that time is limited, so I'm less likely to spend it on something that has the potential drawbacks that I raised. FWIW, yes, I am trying out git on the side. That use of time looks worthwhile.
- grogers 17y agoIts nice to see that subversion as a project is still evolving, but I will continue to use git-svn as my subversion client anyways most likely. They haven't really mentioned exactly what will be supported by these changes, but it seems to me that without local branches, offline commits aren't really worth much. The fact that you need 5 svn checkouts to work on 5 different features at once sucks. With git-svn I can work on as many features as I want with different local branches, and they can each be based on different remote branches if needed.
- kree10 17y agoIt doesn't have to be an either/or. I've been very happy with git-svn as my svn client. It's not git-like, it's actually git.
- InclinedPlane 17y agoGit is basically the epitome of why linux will never have significant marketshare on the desktop. Sure, Git is an amazing tool, but its usability is utterly horrific. And Git's most prominent users tend to be extremely sophisticated and intelligent software developers who are able to come to grips with these usability problems quite easily, so their response to those problems tends to be "get over it, git is great, use it anyway, it's not that big a deal, quit whining" which is no better than "let them eat cake". When people use a computer they want usability, they want a GUI (where relevant), they don't want an ALTAIR front-panel with a bunch of inscrutable toggles and equally inscrutable lights. This is why Mercurial is so popular despite being so similar to Git. Until the Git team accept these problems as real problems and do something about them Git will be relegated to a niche tool and 10 or 20 years down the road when every dev is using DVCS it won't be Git it'll be Mercurial or SVN-DVCS or something new.
- mru 17y agoI guess you hadn't noticed that git has a very nice gui.
- InclinedPlane 17y agoWhich do you mean? Git-GUI is not "very nice" by any means. TortoiseGit is decent but a new Git user is hardly guided there (compare that to: http://mercurial.selenic.com/downloads/ http://mercurial.selenic.com/downloads/). Also, my point wasn't specifically about GUIs per se but about usability overall. Git developers have only very recently, and only very grudgingly it seems, accepted that usability is even a serious concern. Considering that a developer will have an enormous amount of interaction with source control tools (almost as much as with an IDE or build tools in general) usability is obviously a huge factor. Git has a lot of the technical aspects nailed but I would be shocked if it won the current battle for revision control system of the future.
- jrockway 17y agoBut Subversion's UI is horrific and its common operations throw away data in many cases. If Git is the Linux of version control systems, Subversion is the Windows of version control, and I don't mean that as a compliment. At least it's possible to get Linux working.