21–30 of 41 posts
Earlier quoted context omitted.
While switching to a single .svn directory seems good, there's also a feature lost: you can no longer move parts of your working trees around the filesystem without hassle.
This is dangerous and error prone... What use case are you solving for by doing that?
Earlier quoted context omitted.
SVN is very easy to use compared to Git (or Mercurial etc.). This allows my team to provide version control for teams who aren't very technically skilled but who are nevertheless producing content that will appear on our website somewhere (e.g. static content).
Really? I used Subversion for over 4 years and suffered through the regular merge issues, connectivity issues ("huh, can't commit because I'm not connected"), line ending issues, you name the problem I had it. Two days into using Mercurial I felt more confident with it than I had ever felt with Subversion. I could branch code without having to work with the server, I could commit on my own machine and later push chan…
I'm curious, because at least Git does not protect you from CRLF-problems out of the box. All the committers must have right settings (autocrlf=input for unix and true for Windows). In case of a central repository, you probably should have a protection hook in case someones settings get changed anyways.
Earlier quoted context omitted.
Setting up a SVN server takes seconds (infact it comes pre installed on all macs). Setting up a git server is a nightmare. If you have a small team like me (2-3 people max) then SVN easily meets all your needs. Naturally Git will catch up and supersede but currently they are focusing on other stuff.
Why is it a nightmare? You just run `git init --bare` and it all just works. SSH provides authentication, the filesystem provides authorisation. As I remember, svn is more complicated, it has that separate svnadmin tool and relies on you to craft a suitable directory structure.
http://www.timdavis.com.au/git/setting-up-a-msysgit-server-w...
I tried on another ubuntu machine and it just kept failing, I tired around 4 walk throughs and none of them completed... why I'm not sure.
After reinstalling that ubuntu machine after each failure I gave up and went back to SVN because it is already configured on my laptop, and I decided I might as well just use the hackintosh/OSX86 install on my workstation as its primary work environment and use SVN server already available.
I'll try git again at some stage, but I just haven't got enough spare time to spend hours debugging where things aren't as I'd expect at the moment.
Subversion has been "out" for years now! Please move on to a DVCS as soon as you can and leave it to die a respectable death.
I probably should have linked to the release notes instead, which are available here: http://subversion.apache.org/docs/release-notes/1.7.html Some big changes in 1.7 extracted from the release notes: Working Copy Metadata Storage Improvements A key feature of the changes introduced in Subversion 1.7 is the centralization of working copy metadata storage into a single location. Instead of a .svn directory in every di…
I'm not trolling here, this is a genuine question: What are the advantages of using SVN over Git? (assuming one was starting a new project and hadn't yet chosen a VCS)
Earlier quoted context omitted.
One big one is that you can check out a working copy of a particular sub-path in the repository. This means you don't need the whole repo (or the repo's entire history) locally, which is necessary in workflows where build products and other giant binaries are stored in version control. I believe this is why many people still use Subversion and Perforce, etc.
Of course, this is probably a not-so-great reason for doing so and reflects an inability to change build procedures/organizational workflows if this feature is absolutely vital.
* SVN is no simpler than Git
* Working with a team is easier to branch and merge
* The tools and community around Git are vibrant
Go use TRAC and SVN, and then hit yourself in the face with a brick a few times, and see which you enjoy more.
Earlier quoted context omitted.
Why is it a nightmare? You just run `git init --bare` and it all just works. SSH provides authentication, the filesystem provides authorisation. As I remember, svn is more complicated, it has that separate svnadmin tool and relies on you to craft a suitable directory structure.
I'm not going to say you're wrong, I just haven't had a install work as advertised yet. I was initially put off when I tried to install it on my Windows workstation, check out this tutorial for how much of an annoyance it is : http://www.timdavis.com.au/git/setting-up-a-msysgit-server-w... I tried on another ubuntu machine and it just kept failing, I tired around 4 walk throughs and none of them completed... why I'm…
mkdir repository cd repository git init
Then on the client side:
git add serverRemote ssh://user@host.com/path/to/repository
I'm not surprised that it's difficult on Windows, since this simple approach relies on so much stuff that doesn't come with Windows, but on a UNIX server it shuold be really straightforward. Much easier than setting up Subversion in my experience.
Earlier quoted context omitted.
Why is it a nightmare? You just run `git init --bare` and it all just works. SSH provides authentication, the filesystem provides authorisation. As I remember, svn is more complicated, it has that separate svnadmin tool and relies on you to craft a suitable directory structure.
I'm not going to say you're wrong, I just haven't had a install work as advertised yet. I was initially put off when I tried to install it on my Windows workstation, check out this tutorial for how much of an annoyance it is : http://www.timdavis.com.au/git/setting-up-a-msysgit-server-w... I tried on another ubuntu machine and it just kept failing, I tired around 4 walk throughs and none of them completed... why I'm…
- setup or have available another linux machine to act as a "client". git on windows with ssh can be a bit fidgety sometimes, and that would help you debug whether it's a client or server issue.
- do look at gitolite for managing the repos [1]. Its "simple" to install, and the features it brings to the table are awesome (from private 'scratch' repos to auth and key management, and several others).
Earlier quoted context omitted.
Is SVN just slowly evolving DVCS features? That seems to be the progression I've been noticing.
No. They decided to focus on being the best centralized version control system: http://lwn.net/Articles/381794/