From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Scott Chacon <schacon@gmail.com>, git list <git@vger.kernel.org>
Subject: Re: Git Community Book
Date: Tue, 29 Jul 2008 15:47:59 -0700 [thread overview]
Message-ID: <7v1w1cb940.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0807291716460.19665@iabervon.org> (Daniel Barkalow's message of "Tue, 29 Jul 2008 18:34:31 -0400 (EDT)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> In particular, I think it's really useful to show a commit graph with
> branching and merging, and introduce refs as movable pointers to commits
> in the graph, and local branches as refs that you move and tracking refs
> as refs that copy values in other repositories.
I'd very strongly second this. If somebody is really into screencasts
(and especially from the Ruby circle, I would guess), this may be worth
a look:
http://excess.org/article/2008/07/ogre-git-tutorial/
I saw a couple of technical inaccuracies in the presentation (I do not
expect any presentation or screencast to be perfect; I've never seen one
without any technical error anyway, perhaps other than my own at OLS a few
years ago), but otherwise it was very well done. Espcially the part that
builds the commit ancestry chains I was very happy to see it taught like
so.
next prev parent reply other threads:[~2008-07-29 22:49 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 16:20 Git Community Book Scott Chacon
2008-07-29 16:28 ` Miklos Vajna
2008-07-29 17:09 ` Petr Baudis
2008-07-29 18:30 ` Scott Chacon
2008-07-29 18:42 ` Junio C Hamano
2008-07-29 19:00 ` Julian Phillips
2008-07-29 19:09 ` Junio C Hamano
2008-07-30 13:27 ` markdown 2 man, was " Johannes Schindelin
2008-07-30 19:32 ` Junio C Hamano
2008-07-30 23:48 ` Wincent Colaiuta
2008-07-31 0:13 ` Scott Chacon
2008-07-31 0:30 ` Junio C Hamano
2008-07-31 11:24 ` Abdelrazak Younes
2008-07-31 13:01 ` Stephan Beyer
2008-07-31 14:13 ` Abdelrazak Younes
2008-07-31 14:33 ` Abdelrazak Younes
2008-07-31 15:09 ` Miklos Vajna
2008-07-31 15:29 ` Abdelrazak Younes
2008-07-31 19:00 ` Miklos Vajna
2008-08-01 0:45 ` Junio C Hamano
2008-08-01 7:11 ` Abdelrazak Younes
2008-08-01 9:46 ` Thomas Rast
2008-08-01 10:19 ` Abdelrazak Younes
2008-07-31 20:57 ` Jan Krüger
2008-08-01 7:50 ` Abdelrazak Younes
2008-08-01 10:45 ` Dmitry Potapov
2008-08-01 11:06 ` Abdelrazak Younes
2008-07-29 19:34 ` Scott Chacon
2008-07-29 19:57 ` Junio C Hamano
2008-07-30 21:39 ` J. Bruce Fields
2008-07-29 17:43 ` Junio C Hamano
2008-07-29 18:25 ` Junio C Hamano
2008-07-29 19:29 ` Scott Chacon
2008-07-29 19:24 ` Scott Chacon
2008-07-29 22:34 ` Daniel Barkalow
2008-07-29 22:47 ` Junio C Hamano [this message]
2008-07-30 13:20 ` Bart Trojanowski
2008-07-30 18:27 ` Junio C Hamano
2008-07-30 13:31 ` Bart Trojanowski
-- strict thread matches above, loose matches on Subject: below --
2008-09-05 19:08 Scott Chacon
2008-09-05 19:15 ` Thomas Adam
2008-09-05 20:45 ` Scott Chacon
2008-09-05 19:41 ` Junio C Hamano
2008-09-05 21:34 ` Scott Chacon
2008-09-05 22:09 ` Felipe Contreras
2008-09-06 6:33 ` Shawn O. Pearce
2008-09-06 18:14 ` Scott Chacon
2008-09-05 20:27 ` Linus Torvalds
2008-09-06 0:48 ` Stephan Beyer
2008-09-06 18:26 ` Christos Τrochalakis
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=7v1w1cb940.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=schacon@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 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.