From: Jakub Narebski <jnareb@gmail.com>
To: Dmitry Potapov <dpotapov@gmail.com>
Cc: Tim Harper <timcharper@gmail.com>, git@vger.kernel.org
Subject: Re: Why is it important to learn git?
Date: Wed, 22 Jul 2009 14:44:23 -0700 (PDT) [thread overview]
Message-ID: <m3my6wbdfs.fsf@localhost.localdomain> (raw)
In-Reply-To: <20090722210738.GA25324@dpotapov.dyndns.org>
Dmitry Potapov <dpotapov@gmail.com> writes:
> On Tue, Jul 21, 2009 at 11:08:31PM -0600, Tim Harper wrote:
> >
> > How has mastering the advanced features of git helped you to be a
> > better programmer?
>
> I don't think that features itself make as big difference as the fact
> Git provides you much more flexibility in choosing a more appropriate
> workflow than you have with any centralized VCS. (Yes, you will still
> find many Git features handy even if you work with it as you did with
> CVS, but you will miss most benefits of Git).
>
> To really understand what benefits Git offers, you have to realize first
> what is wrong CVS and CVS-like VCSes. Unfortunately, it is difficult to
> explain just in a few words. Some implementation deficiency of CVS is
> obvious (and it was addressed in some CVS clones like Subversion), but
> more fundamental problems are far less obvious even for people who used
> CVS for many years.
See also my answer for "Difference between GIT and CVS" question
at StackOverflow:
http://stackoverflow.com/questions/802573/difference-between-git-and-cvs/824241#824241
> To be fair to CVS, it is far from the worst VCS. There are some insane
> lock-based VCS, which were so painful to use (mostly due to these
> exclusive locks but often due to some other insanity too) that anyone
> who worked with may think about CVS as a really nice system...
By the way, even if CVS didn't implement support for file renames and
copying, at least it provides support for file deletion (as opposed to
*khem* SourceSafe).
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-07-22 21:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 5:08 Why is it important to learn git? Tim Harper
2009-07-22 7:52 ` Thomas Rast
2009-07-22 18:15 ` Sverre Rabbelier
2009-07-22 21:47 ` Jakub Narebski
2009-07-23 5:00 ` Jeff King
2009-08-04 14:09 ` Andreas Ericsson
2009-07-22 18:31 ` Scott Chacon
2009-07-22 21:07 ` Dmitry Potapov
2009-07-22 21:44 ` Jakub Narebski [this message]
2009-07-22 21:50 ` Allan Kelly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3my6wbdfs.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=timcharper@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).