From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC] Managing projects - advanced Git tutorial/walkthrough
Date: Sat, 6 May 2006 21:34:56 -0400 [thread overview]
Message-ID: <20060507013455.GB5709@fieldses.org> (raw)
In-Reply-To: <7v64kisyow.fsf@assigned-by-dhcp.cox.net>
On Sat, May 06, 2006 at 01:09:03PM -0700, Junio C Hamano wrote:
> - Understanding git as an end user. Currently, this is
> included in the global map git(7) documentation. It might
> make sense to separate it out. This should talk about
> concepts like blobs/trees/commits/trust/index without going
> into lowlevel details of the implementation. The stress
> should be on what they are for, not operationally but
> philosophically. What's currently in README would be
> suitable for this part, with some additional topics:
Yeah, I actually made a start at a sequel to tutorial.txt, with the goal
that after reading the sequel a user would have encountered the main
concepts necessary to read any of the man pages--mainly the object
database and the index file. My work so far is in the
"advanced-tutorial" branch of
git://linux-nfs.org/~bfields/exports/git.git
but it needs some cleaning up.
I was hoping I'd be able to replace some of the README or
core-tutorial.txt in the process, but the latter has a lot of
git-hacker-only detail in it, and the former is a bit more verbose and
has some motivation (explaining why stuff was designed the way it was)
that is nice but maybe not necessary for a minimal tutorial.
--b.
prev parent reply other threads:[~2006-05-07 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 8:43 [RFC] Managing projects - advanced Git tutorial/walkthrough Jakub Narebski
2006-05-06 20:09 ` Junio C Hamano
[not found] ` <20060506175450.57b70ee2.seanlkml@sympatico.ca>
2006-05-06 21:54 ` sean
2006-05-07 1:34 ` J. Bruce Fields [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=20060507013455.GB5709@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=junkio@cox.net \
/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).