git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Chacon <schacon@gmail.com>
To: Tim Harper <timcharper@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Why is it important to learn git?
Date: Wed, 22 Jul 2009 11:31:00 -0700	[thread overview]
Message-ID: <d411cc4a0907221131q28ffb24av8715c4497f50deb3@mail.gmail.com> (raw)
In-Reply-To: <e1a5e9a00907212208t10a071d0oe59a39b357a1111a@mail.gmail.com>

Hey,

On Tue, Jul 21, 2009 at 10:08 PM, Tim Harper<timcharper@gmail.com> wrote:
> Hi all,
>
> I'm preparing to teach a workshop on git, and would like to know how
> other people benefit from the advanced features of git.  So, if you're
> feeling kind enough to share a few minutes to respond (which I will
> receive with gratitude):
>
> How has mastering the advanced features of git helped you to be a
> better programmer?

I think the biggest gain Git gives many developers over other VCSs
(even other DVCSs) is the lightweight branching flexibility and easy
merging.  In Git, lightweight branches or topic branches are used in
much the same way that patch queuing tools like Hg's mq extension or
quilt, but I think most users find them much, much easier to use and
understand and often less error prone.  Using branches as silos
dedicated to a single work topic and being able to easily keep them
separated until you are ready to apply them to a main line of work
(such as merging with your master branch) is very powerful and is done
via a very simple and understandable existing paradigm of branches
rather than trying to learn a whole new command set of patching.  This
allows for fast and simple context switching and work unit isolation
that both very definitively changes most developers workflows in ways
that were completely impossible in SVN or Perforce or what-have-you.

Hope that helps.  If you need any material for your workshop, I have a
number of slides (Keynote and PDF) for presentations I have given at:

http://github.com/schacon/git-presentations

You can also get the PDF of the slides of the tutorial I gave at OSCON
yesterday on Git here:

http://en.oreilly.com/oscon2009/public/schedule/detail/7953

Let me know if there is anything else I can do to help.

Thanks,
Scott

  parent reply	other threads:[~2009-07-22 18:31 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 [this message]
2009-07-22 21:07 ` Dmitry Potapov
2009-07-22 21:44   ` Jakub Narebski
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=d411cc4a0907221131q28ffb24av8715c4497f50deb3@mail.gmail.com \
    --to=schacon@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).