From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff King Subject: Re: [doc] User Manual Suggestion Date: Fri, 24 Apr 2009 10:11:39 -0400 Message-ID: <20090424141139.GC10761@coredump.intra.peff.net> References: <20090423175717.GA30198@fieldses.org> <20090423201636.GD3056@coredump.intra.peff.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: "J. Bruce Fields" , David Abrahams , git@vger.kernel.org To: Michael Witten X-From: git-owner@vger.kernel.org Fri Apr 24 16:16:52 2009 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1LxM9W-0005PB-Ol for gcvg-git-2@gmane.org; Fri, 24 Apr 2009 16:13:19 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759497AbZDXOLu (ORCPT ); Fri, 24 Apr 2009 10:11:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759484AbZDXOLt (ORCPT ); Fri, 24 Apr 2009 10:11:49 -0400 Received: from peff.net ([208.65.91.99]:59248 "EHLO peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759458AbZDXOLs (ORCPT ); Fri, 24 Apr 2009 10:11:48 -0400 Received: (qmail 28650 invoked by uid 107); 24 Apr 2009 14:11:56 -0000 Received: from coredump.intra.peff.net (HELO coredump.intra.peff.net) (10.0.0.2) by peff.net (qpsmtpd/0.40) with (AES128-SHA encrypted) SMTP; Fri, 24 Apr 2009 10:11:56 -0400 Received: by coredump.intra.peff.net (sSMTP sendmail emulation); Fri, 24 Apr 2009 10:11:39 -0400 Content-Disposition: inline In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Thu, Apr 23, 2009 at 03:45:46PM -0500, Michael Witten wrote: > However, a discussion of blobs, trees, commits, objects, and > references isn't necessarily low-level. It seems to me that it is a > high-level understanding of the git world. Without those > *definitions*, people are left to their own wrong, inconsistent > thoughts. > > The low-level stuff is HOW those concepts have been used in the > implementation of git: Where certain files are stored, how certain > bytes are organized in memory, what are the underlying porcelain > tools, etc. That what's low-level. I think I wasn't clear in my original message. I didn't mean teaching low-level stuff like plumbing or file layouts. By "bottom-up" I really meant teaching concepts (like objects, their types, and references), from which user operations and workflows can be explained (or often deduced by the user). Whereas a top-down approach would _start_ with workflows and say "To accomplish X, do Y". So I think we are in agreement about the right "level" to start at. -Peff