Re: What's cooking in git.git (topics)

From: J. Bruce Fields <bfields@fieldses.org>
Date: Nov 29, 2007, 01:06 UTC
Message-ID: <20071129010606.GA5856@fieldses.org>
In-Reply-To: <7vlk8hzx0g.fsf@gitster.siamese.dyndns.org>

On Wed, Nov 28, 2007 at 05:00:15PM -0800, Junio C Hamano wrote:

Show 16 quoted lines

> Nicolas Pitre <nico@cam.org> writes:
> 
> > ...  In all the tutorials for $job I've done so 
> > far, I simply never talk about pull nor clone, but rather about init, 
> > "git remote", fetch and merge, with explicit and meaningful branch 
> > names.  I think that basic commands, even if there is a bit more of 
> > them, make Git easier to learn and understand than talking about those 
> > magic meta commands hiding the truth away.
> 
> That's actually a quite interesting approach for teaching.
> 
> The original "tutorial" (now core-tutorial) was similar in spirit; it
> built the user experience by starting at sequence of low level commands,
> and then finally said "since this is so often used combination, there is
> a short-hand for it that does all".  I think the approach would work
> quite well for people who want to use the tool with deep understanding.

Yeah. I considered doing the above some time ago and ran into some differences between git-clone and "git init && git remote add && git fetch"--I think it may have just been that the latter didn't guess the HEAD in the same way. That's fixed now, right? Is there any other difference people would run into? If not, I'll work on that. I wouldn't want to break things down quite as far as the core-tutorial, but this particular thing is so simple....

--b.