From: "Scott Chacon" <schacon@gmail.com>
To: "git list" <git@vger.kernel.org>
Subject: Git Community Book
Date: Tue, 29 Jul 2008 09:20:20 -0700 [thread overview]
Message-ID: <d411cc4a0807290920p62f5d7e1r727a62ef2b4611fc@mail.gmail.com> (raw)
So I wanted to develop a really nice, easy to follow book for Git
newcomers to learn git quickly and easily. One of the issues I
remember having when learning Git is that there is a lot of great
material in the User Guide, Tutorial, Tutorial 2, Everyday Git, etc -
but they're all huge long documents that are sometimes difficult to
come back to and remember where you were, and I didn't know which one
to start with or where to find what I was looking for, etc.
So, what I've started to do is pull material from all of them into a
single book which will be available in online HTML (one page per
chapter) and downloadable PDF form. I'm trying to give it a very
organized flow that will hopefully be a bit easier to follow and
digest than the current formats, and including a number of diagrams,
illustrations and screencasts to supplement the text. Where possible,
I am also trying to simplify the explanations a bit to be a tad more
digestible for beginning users, at least in the first couple dozen
chapters. I have put the current html output of this book here:
http://book.git-scm.com
It is not complete - the grey links are chapters that are very short
or completely empty - but it is a start. Please let me know what you
think, and if anyone is interested in helping with the project, give
me a shout.
Also, for credit, I have generated an Authors page I will be linking
to the site soon that lists everyone that contributed a patch to any
of the Git User Guide, Git Tutorials, etc. It is in the PDF right
now, but not in the HTML version yet (and the PDF is not yet linked to
the site).
Thanks,
Scott
next reply other threads:[~2008-07-29 16:21 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 16:20 Scott Chacon [this message]
2008-07-29 16:28 ` Git Community Book 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
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=d411cc4a0807290920p62f5d7e1r727a62ef2b4611fc@mail.gmail.com \
--to=schacon@gmail.com \
--cc=git@vger.kernel.org \
/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).