Re: [PATCH] Add a birdview-on-the-source-code section to the user manual

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: May 9, 2007, 09:33 UTC
Message-ID: <Pine.LNX.4.64.0705091127310.4167@racer.site>
In-Reply-To: <7v4pmmzivz.fsf@assigned-by-dhcp.cox.net>

Hi,

On Tue, 8 May 2007, Junio C Hamano wrote:

Show 20 quoted lines

> Junio C Hamano <junkio@cox.net> writes:
> 
> > "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.
> 
> Having said that, I do not think the patch belongs to the "git USER'S 
> manual".  It is a very good introductory material for a separate "git 
> hackers manual", though.

That is what I was referring to when I mentioned "no outcry". Bruce said that he liked the idea to have something like that in the USER's manual.

And I have to agree: There might be enough room to actually go and write a Git hacker's manual, but IMHO that takes a lot of time which has to be found at first.

And even if we actually have such a hacker's manual one day, this "sneak preview" in the user's manual does not hurt, but could actually entice people to read that manual, too.

Ciao, Dscho