Version Control and Hosting

I know that this question has been asked many times before in different guises and that I am an ignorant n00b, thinking that I can add something to the discussion. However, I am interested not only in the version control system, but also its hosting options, compatible applications and compatibility with Windows.

If you do not have experience with multiple systems, tell me what you are using: version control system, code hosting, implementation (vc program) and OS.

I have only a few limitations:

  • I would like to use a program that works well on both Linux and Windows. This means at least the equivalent command line interface.
  • Implementations should be stable enough that I do not need to constantly recompile files on Linux, and I never have to compile on Windows.
  • For version control, there must be at least one compatible free hosting for sites (for open source projects). If the hosting site is open source, this will be ideal.
  • The version control standard must be open.

Sorry if I say as a demanding brother, inviting other people to make his decisions. I just want to learn from your experience, so I don’t need to switch back to version control systems.

What major version of Windows version control system would you recommend?

+4
source share
3 answers

First, you can benefit from this recently published article in the ACM queue:
The feel of version control systems

I will talk about the two that I know most about, the others will tell about everything else.

SVN:

GIT:

  • Extremely powerful SCM
  • A complete history of sources in each scan of the source tree.
  • Not the biggest support for Windows, but it is currently making big improvements. http://code.google.com/p/msysgit/
  • Many free hosts: github , repo.or.cz
  • The current "cool guy" on the bokeh.

Looks like you just want to go with svn. It sounds like you just want to have version control material, so you don’t have to worry about the learning curve associated with GIT.

Others, things to see, but I did not detail due to the general lack of window tools: Mercurial, Darcs, Bazaar. If you check Mercurial, you can use bitbucket and google code as a host.

+5
source

One of the most used / known version control systems, probably Subversion (SVN)

I use it every day both on Linux and on Windows (for personal and professional projects), both in the CLI and in graphical tools.

  • Windows: I often use TortoiseSVN
  • Windows / Linux: I usually work with Eclipse, and its Subversive plugin
  • Windows / Linux: The "svn" command in the CLI is great too, especially if you want to use some scripts to automate struff.

Note that I never had to compile anything for SVN to work (on Windows, using TortoiseSVN, everything is fine; on Linux Ubuntu, the packages bundled with Ubuntu are also fine)


For hosting, since SVN is used by many projects, you have many options, especially for open source projects.

  • For example, Google code allows you to use SVN to host your projects.
  • Same for SourceForge ( see ), if I remember correctly.
  • You have other possibilities, of course, for example, Assembla


If you want to use the Distributed revision control software for something, you can take a look at tools like Bazaar , Mercurial, and / or Git . Each of them is used by some large projects (well, at least for Bazaar (MySQL uses this, I think) and Git (this is the Linux kernel)).

I used Bazaar for Linux and Windows, but only on the command line; there has never been any problem with this. I know that there are graphical tools for Linux and Windows, but I have never used them, so I can not say more.


However, if you do not need a distributed system, I would go with Subversion, absolutely without hesitation.

+4
source

I use Git , mainly because I develop on many workstations (at home or at work), and DVCS is much easier for replicating my repository, as well as for branching, merging, and speed for initializing and importing code into a new repository.

  • I would like to use a program that works well on both Linux and Windows. This means at least the equivalent command line interface.

" git " is your CLI and runs in a DOS session as well as in bash.

  • Implementations must be stable enough that I don’t need to constantly recompile Linux, and I never have to compile on Windows.

msysgit is now pretty stable on Windows, as stated in the question β€œ Git under windows: MSYS or Cygwin? ” (no need for Cygwin).

  • For version control, there must be at least one compatible free hosting for sites (for open source projects). If the hosting site is open source, this will be ideal.

GitHub is a good example of free code hosting.

  • The version control standard must be open.

Check out the Git sources at git.git .

+2
source

All Articles