Git is certainly a bit harder to learn than SVN, but it is so much more
git's strength is that it works seamlessly as a single-user system and and
a multi-user + server system.
I use git to track changes during development even if I never move it from
the original PC.
Git has the added benefit that all clones are "equal". If you lose an SVN
server you're screwed. With git you can just reclone it from a developer
Git is a far better solution in the long term.
On Thu, Jun 12, 2014 at 3:03 AM, Dale R. Worley <wor...@alum.mit.edu> wrote:
> > From: HOWARD ROSENBLOOM <hrsn...@gmail.com>
> > We are a small company that has not been using any form of
> > configuration/tracking in the past. We have 2-3 programmers and have
> > into the situation where we need to get control of any work being done.
> > Since none of us have any experience in this area I am looking for
> > suggestions as to whether GIT is right for what we are looking for, or is
> > there a better/more appropriate solution.
> I've used both Git and Subversion. If you're a small operation, and
> you've not used version control before, and if you do not need the
> distributed development facilities of Git, I believe that you'll find
> Subversion easier to learn and use. The drawback of Subversion is
> that you need to have a server that is accessible by each worker for
> all check-ins and check-outs.
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.