On 26/1/10 02:54, "Luisgo" <lgo...@gmail.com> wrote:

> Hi all,
> I've been using git for over a year now and have nothing but great
> things to say about it. But every once in a while I start thinking of
> my workflow and how to improve it along with my use of git and other
> things. A questions that I keep trying to answer is what a commit
> should be. I know what it is technically but in theory what should I
> commit? A feature? My daily changes? What if it's a change I haven't
> finished?
> How do you define a commit?

I'd like to know this too. I know the technicalities to some extent, but as
a lone, self-taught, web builder I'm vague about good practice at the
day-to-day practicalities level.

I'd like to see a set of exemplar commits for *something I understand* such
as website development. I have seen examples, but they tend to be for things
like the Linux kernel which are way over my head.

Roddie Grant

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to