Re: yet another workflow question...

From: Wincent Colaiuta <win@wincent.com>
Date: Oct 11, 2007, 14:39 UTC
Message-ID: <00CC9676-C6D8-4E9E-ABE3-A6238810B536@wincent.com>
In-Reply-To: <e2a1d0aa0710110711m77ca967bmd1d5ffd5d3099aab@mail.gmail.com>

El 11/10/2007, a las 16:11, Patrick Doyle escribió:

Show 7 quoted lines

> Sorry for cluttering up the list with yet another very basic workflow
> question, but I'm still struggling with finding an answer to the
> burning question, "What can git do for me?"  (So far, I have come to
> the conclusion that, for my simple, single developer, branchless,
> linear projects, there's not much that git can do for me that any
> other SCM could do for me.  It appears to have been designed to solve
> problems for which I have absolutely no appreciation whatsoever. :-))

Even with the workflow you describe, Git brings some nice benefits:

1. Faster than anything else out there
2. You can work offline (even if you have an "always on" net  
connection, think about the times when it goes down)
3. You can easily amend mistakes in your last commit (git-commit -- 
amend)
4. You can easily stash away work in progress and go off on a tangent  
(git-stash)
5. You get nice colorized diff and log output for free
6. Great visualization tools included for free (gitk, git-gui etc)

And those are just a few off the top of my head. The more you work with Git, the more benefits you will discover, even if you're not trying to do anything fancy with it. And although you are currently using branchless development, you may find with time that you start using things like topic branches simply because Git makes it so darn easy to do so, and the benefit is that you'll keep your history much cleaner and easier to understand when you go back to look at it later on.

Cheers, Wincent