On Fri, 24 Apr 2009, Jeff King wrote: > On Fri, Apr 24, 2009 at 05:34:00PM -0400, Daniel Barkalow wrote: > > > I'd say that blobs and trees are an implementation detail of "the full > > content of a version of the project", not something conceptually > > important. Likewise, the date representation used in commits isn't > > I disagree. I think it's important to note that trees and blobs have a > name, and you can refer to them. Once you know that, the fact that you > can do: > > 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). > > No, that isn't critical for understanding how _commit_ operations work, > but I think that is exactly the sort of conceptual knowledge that let > people use git more fully. Yeah, I'll agree with that. They're good to explain as "these are things git can tell you about", but they're not relevant to the discussion of "what is history". (And, actually, I think git has a few usability warts due to relying too much on command line arguments being objects; it would be quite nice if "git blame 1a2b3c:Makefile" worked despite this technically being incoherent.) -Daniel *This .sig left intentionally blank* -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html