Re: [doc] User Manual Suggestion

From: Michael Witten <mfwitten@gmail.com>
Date: Apr 25, 2009, 00:26 UTC
Message-ID: <b4087cc50904241726l1b38495apf3df4d8e10254902@mail.gmail.com>
In-Reply-To: <4E155CC5-B20A-4B79-8CBF-9D1E0E36920F@boostpro.com>

On Fri, Apr 24, 2009 at 19:19, David Abrahams <dave@boostpro.com> wrote:

Show 10 quoted lines

>>  git show master
>>  git show master:Documentation
>>  git show master:Makefile
>>
>> just makes sense. You are always just specifying an object, but the type
>> is different for each (and show "does the right thing" based on object
>> type).
>
> I don't believe you need to know about trees and blobs to make sense of
> that.  Those are just directories and files.

I still think the key is that commits and blobs and trees are all objects, and the important things are the concepts of objects, object addresses, object pointers, and handles (or, what everyone else calls objects, object names, references, and symbolic references).

Also, you've mixed in the theory of file system addressing in with the theory of git addressing. I think it's important to realize that the tool 'git show' is actually providing a translation between the two worlds. There's not really any need for paths to be considered a fundamental git concept; simply, git tools know how to translate between both worlds.