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

Re: Comments on Presentation Notes Request.

From
Jakub Narebski <jnareb@gmail.com>
Date
Jan 9, 2009, 13:50 UTC
Message-ID
<m31vvc37x0.fsf@localhost.localdomain>
In-Reply-To
<c115fd3c0901061433i78bf3b26v77e5981aada6728e@mail.gmail.com>
"Tim Visher" <tim.visher@gmail.com> writes:
Show 10 quoted lines
> Hello Everyone,
> 
> I'm putting together a little 15 minute presentation for my company
> regarding SCMSes in an attempt to convince them to at the very least
> use a Distributed SCMS and at best to use git.  I put together all my
> notes, although I didn't put together the actual presentation yet.  I
> figured I'd post them here and maybe get some feedback about it.  Let
> me know what you think.
> 
> Thanks in advance!
Take a look at the following links:
 * "Understanding Version-Control Systems (DRAFT)" by Eric Raymond
   http://www.catb.org/esr/writings/version-control/version-control.html
 * "Version Control Habits of Effective Developers" at The Daily Build
   http://blog.bstpierre.org/version-control-habits
Note that the first one is DRAFT; on the other hand it explains
lock-edit, merge-then-commit, and commit-then-merge workflows quite
well, and has a host of links.
   
-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Daniel Barkalow
Message 10 of 10 in “Comments on Presentation Notes Request.”
  1. Tim VisherJan 6, 2009
  2. Jeff KingJan 7, 2009
  3. Daniel BarkalowJan 7, 2009
  4. Boyd Stephen Smith Jr.Jan 7, 2009
  5. Daniel BarkalowJan 8, 2009
  6. Jeff KingJan 8, 2009
  7. david@lang.hmJan 7, 2009
  8. Tim VisherJan 7, 2009
  9. Daniel BarkalowJan 8, 2009
  10. Jakub NarebskiJan 9, 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.