4 ms·
> Subversion uses copy-on-write when creating a branch, so it is not expensive It doesn't matter what the server does, it's relatively slow on the client to ei
by taspeotis 13y ago
> Subversion uses copy-on-write when creating a branch, so it is not expensive
It doesn't matter what the server does, it's relatively slow on the client to either switch to or checkout a branch.
- raimue 13y agoOn the plus side, you can have multiple local branches side-by-side with svn easily, which is much easier to work with for beginners as they can just view and compare the trees in the filesystem. With git, such a setup requires more understanding on how to make a local clone instead of fetching the full history from the server multiple times.
- Dylan16807 13y agoFetching the full history in git is often less data than a checkout in svn. Also you could just copy the folder. Edit: git-new-workdir looks like it makes things convenient.
- millstone 13y agoWith git, you typically have a single checkout of the repo. But with svn, it's natural to have separate checkouts of each branch you care about, in separate directories. So a typical "switch" in svn is not a switch at all: you just start working on files in a separate directory, or even simultaneously on two separate checkouts (which is more awkward in git). I use and like git, but multiple checkouts is one aspect of the svn workflow that I miss.
- richardwhiuk 13y agoThere's no problem with having multiple clones of a git repository on a single machine.
- taspeotis 13y agoYou're making my point for me. In typical Subversion client usage the server's CoW optimisations mean nothing. If you have to check out each branch you make, using Subversion gets really slow, really quickly.