git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] Add a birdview-on-the-source-code section to the user manual
Date: Tue, 08 May 2007 21:06:46 -0700	[thread overview]
Message-ID: <7vps5azlm1.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070509031803.GA27980@fieldses.org> (J. Bruce Fields's message of "Tue, 8 May 2007 23:18:04 -0400")

"J. Bruce Fields" <bfields@fieldses.org> writes:

> The organization of the next bit is slightly confusing: we're set up to
> expect a longer lecture on the revision walker, but instead there's just
> the historical note on git-rev-list, a mention of 'revision.c',
> 'revision.h', and 'struct rev_info', and then it rapidly digresses into
> discussing builtins.

I had the same impression.

I was meaning to write a "code walkthru for git hackers and
wannabes" with target audience quite different from the
user-manual.  My idea of which areas to cover in what order
seems to match with what Johannes started.

 - sha1_name.c;

 - read_sha1_file();

 - revision.c::setup_revisions() to talk about parsing but not
   about walking yet.

 - start from builtin-merge-base.c into commit.c to talk about
   revision traversal done by get_merge_bases().  This codepath
   is much simpler than the revision.c machinery and is a good
   primer to understand the latter.

 - builtin-diff-tree.c to show one tree and two tree cases, go
   into log-tree.c then tree-diff.c to show the use of
   add_remove() and change() callbacks, and then finally talk
   about diff_flush(), without talking about diffcore
   transformations yet.

 - start from builtin-log.c to review the setup_revisions(),
   then talk about prepare_revision_walk() and get_revision()
   machinery, first pass without talking about path limiting and
   then with path limiting.

 - fetch-pack.c and upload-pack.c to talk about the native
   protocol over ssh and local forking, how revision traversal
   machinery is used, the "objects pointed by refs are complete"
   contract.

 - daemon.c to see how upload-pack is invoked.

 - read_cache(), active_cache[], active_nr and friends;

 - update-index and write-tree, including how cache-tree
   optimizes tree writing after small updates.  Advanced students
   can also look at git-apply here.

 - unpack-trees.c and builtin-read-tree.c to talk about index stages.

 - diffcore transformations, especially diffcore-rename.

 - merge-recursive

  reply	other threads:[~2007-05-09  4:07 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 15:10 [PATCH] Add a birdview-on-the-source-code section to the user manual Johannes Schindelin
2007-05-08 21:01 ` Karl Hasselström
2007-05-08 21:07   ` Johannes Schindelin
2007-05-08 21:31     ` Karl Hasselström
2007-05-08 23:10       ` Johannes Schindelin
2007-05-08 23:22         ` Karl Hasselström
2007-05-09  4:54         ` Daniel Barkalow
2007-05-09  6:31           ` Karl Hasselström
2007-05-09  9:38           ` Johannes Schindelin
2007-05-09 10:43             ` Karl Hasselström
2007-05-09  3:18 ` J. Bruce Fields
2007-05-09  4:06   ` Junio C Hamano [this message]
2007-05-09  5:05     ` Junio C Hamano
2007-05-09  9:33       ` Johannes Schindelin
2007-05-09 17:36       ` J. Bruce Fields
2007-05-09  6:48   ` Karl Hasselström
2007-05-09  9:27   ` Johannes Schindelin
2007-05-09 12:19   ` Johannes Schindelin
2007-05-09 12:32     ` Petr Baudis
2007-05-09 12:50       ` Johannes Schindelin
2007-05-09 16:18         ` Daniel Barkalow
2007-05-09 16:25           ` Johannes Schindelin
2007-05-09 17:07             ` J. Bruce Fields
2007-05-09 20:15               ` Johannes Schindelin
2007-05-09 20:32                 ` J. Bruce Fields
2007-05-09 20:45                 ` Daniel Barkalow
2007-05-09 22:23                   ` Johannes Schindelin
2007-05-10 20:01                     ` Karl Hasselström
2007-05-09 13:18     ` J. Bruce Fields
2007-05-10  4:15       ` Junio C Hamano
2007-05-10 10:36         ` Johannes Schindelin
2007-05-10 20:42           ` Junio C Hamano
2007-05-10 21:14             ` Karl Hasselström

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=7vps5azlm1.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=bfields@fieldses.org \
    --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).