| Both sides previous revision Previous revision Next revision | Previous revision |
| docs:git:git_vs_svn [2010/03/05 15:56] – billh | docs:git:git_vs_svn [2010/03/05 16:00] (current) – billh |
|---|
| * tortoisesvn on windows is awesome (tortoisegit is available, but not as refined just yet) | * tortoisesvn on windows is awesome (tortoisegit is available, but not as refined just yet) |
| * you can version an empty directory (with git, you need to do something like add a .gitignore file to the folder). In case you are wondering why anyone would want to version an empty folder, it could be for something like a log folder or conf folder where files shouldn't be versioned. | * you can version an empty directory (with git, you need to do something like add a .gitignore file to the folder). In case you are wondering why anyone would want to version an empty folder, it could be for something like a log folder or conf folder where files shouldn't be versioned. |
| * since the repository can be controlled by an admin, you can ensure that every developer's commits always exist. With git you have the option to actually "reset" the repository to a previous state. In svn, you need to merge an older revision and commit it in order to "go back in time". FIXME - this is all assuming that the shared git folder is just a publicly available folder. This all may be the same if using apache or a git daemon. | * since the repository can be controlled by an admin, you can ensure that every developer's commits always exist. With git you have the option to actually "reset" the repository to a previous state. In svn, you need to merge an older revision and commit it in order to "go back in time". |
| * since you have a central repository, each commit is automatically giving you a "backup" of your work | * since you have a central repository, each commit is automatically giving you a "backup" of your work |
| |
| ===== svn cons ===== | ===== svn cons ===== |
| * it is common for the sake of administration to keep few repositories. This causes totally unrelated projects to be stored in that repository, such as the development of web sites for clients. Once development of a site is finished, it may never be needed again, but it will always remain and take up space in the svn repository. Since it is advised for git to be used on a project by project basis, all you need to do is delete the project directory. | * it is common for the sake of administration to keep few repositories. This causes totally unrelated projects to be stored in that repository, such as the development of web sites for clients. Once development of a site is finished, it may never be needed again, but it will always remain and take up space in the svn repository. In contrast, since it is advised for git to be used on a project by project basis, all you need to do in git is delete the project directory. |
| |