All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Thomas Rast <trast@student.ethz.ch>,
	Tim Harper <timcharper@gmail.com>,
	git@vger.kernel.org
Subject: Re: Why is it important to learn git?
Date: Wed, 22 Jul 2009 14:47:05 -0700 (PDT)	[thread overview]
Message-ID: <m3iqhkbdb9.fsf@localhost.localdomain> (raw)
In-Reply-To: <fabb9a1e0907221115x212c4b52q47cac29cf0336fc@mail.gmail.com>

Sverre Rabbelier <srabbelier@gmail.com> writes:
> On Wed, Jul 22, 2009 at 07:52, Thomas Rast<trast@student.ethz.ch> wrote:

> >  Learning to make nice, reviewable, working, one-change-per-revision
> >  commits.
> 
> I very much agree with those values, but also
> 
>   Commit early, commit often
 
I also find commit message convention: "short one-line description,
separated by empty line, then more detailed description" to be very
useful (git tools assume and expect this convention).  It helps
keeping changesets / commits small; if you can't write oneline summary
of commit, it is probably too large :-)

-- 
Jakub Narebski
Poland
ShadeHawk on #git

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

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=m3iqhkbdb9.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=srabbelier@gmail.com \
    --cc=timcharper@gmail.com \
    --cc=trast@student.ethz.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.