git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Allan Kelly <allankelly@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Dmitry Potapov <dpotapov@gmail.com>,
	Tim Harper <timcharper@gmail.com>,
	git@vger.kernel.org
Subject: Re: Why is it important to learn git?
Date: Wed, 22 Jul 2009 22:50:37 +0100	[thread overview]
Message-ID: <9586f3420907221450p6b9df86cy62e1832d06150286@mail.gmail.com> (raw)
In-Reply-To: <m3my6wbdfs.fsf@localhost.localdomain>

Has anyone done a presentation on this (very interesting) subject with examples?

What's good about this practice/pattern?
What's bad about that practice/pattern?

I ask because if not, I'd like to - with your help!

Cheers, al.

2009/7/22 Jakub Narebski <jnareb@gmail.com>:
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

      reply	other threads:[~2009-07-22 21:50 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
2009-07-22 21:50     ` Allan Kelly [this message]

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=9586f3420907221450p6b9df86cy62e1832d06150286@mail.gmail.com \
    --to=allankelly@gmail.com \
    --cc=dpotapov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --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).