git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Why is it important to learn git?

From
Jakub Narebski <jnareb@gmail.com>
Date
Jul 22, 2009, 21:47 UTC
Message-ID
<m3iqhkbdb9.fsf@localhost.localdomain>
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:
Show 6 quoted lines
> >  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
Previous: Sverre RabbelierNext: Jeff King
Message 4 of 10 in “Why is it important to learn git?”
  1. Tim HarperJul 22, 2009
  2. Thomas RastJul 22, 2009
  3. Sverre RabbelierJul 22, 2009
  4. Jakub NarebskiJul 22, 2009
  5. Jeff KingJul 23, 2009
  6. Andreas EricssonAug 4, 2009
  7. Scott ChaconJul 22, 2009
  8. Dmitry PotapovJul 22, 2009
  9. Jakub NarebskiJul 22, 2009
  10. Allan KellyJul 22, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.