From: Jakub Narebski <jnareb@gmail.com>
To: "Tim Visher" <tim.visher@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Comments on Presentation Notes Request.
Date: Fri, 09 Jan 2009 05:50:40 -0800 (PST) [thread overview]
Message-ID: <m31vvc37x0.fsf@localhost.localdomain> (raw)
In-Reply-To: <c115fd3c0901061433i78bf3b26v77e5981aada6728e@mail.gmail.com>
"Tim Visher" <tim.visher@gmail.com> writes:
> 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
prev parent reply other threads:[~2009-01-09 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 22:33 Comments on Presentation Notes Request Tim Visher
2009-01-07 6:36 ` Jeff King
2009-01-07 22:30 ` Daniel Barkalow
2009-01-07 22:40 ` Boyd Stephen Smith Jr.
2009-01-08 0:28 ` Daniel Barkalow
2009-01-08 9:56 ` Jeff King
2009-01-07 8:33 ` david
2009-01-07 16:11 ` Tim Visher
2009-01-08 0:14 ` Daniel Barkalow
2009-01-09 13:50 ` Jakub Narebski [this message]
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=m31vvc37x0.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=tim.visher@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).