git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Potapov <dpotapov@gmail.com>
To: George Dennie <gdennie@pospeople.com>
Cc: git@vger.kernel.org, B.Steinbrink@gmx.de,
	"'Jason Sewall'" <jasonsewall@gmail.com>,
	"'Jakub Narebski'" <jnareb@gmail.com>, "'Jan Krüger'" <jk@jk.gs>,
	torvalds@osdl.org
Subject: Re: Hey - A Conceptual Simplication....
Date: Fri, 20 Nov 2009 05:31:04 +0300	[thread overview]
Message-ID: <20091120023103.GC22556@dpotapov.dyndns.org> (raw)
In-Reply-To: <00d401ca6954$a29fa020$e7dee060$@com>

On Thu, Nov 19, 2009 at 03:12:35PM -0500, George Dennie wrote:
> 
> I think an important piece of conceptual information missing from the docs
> is a concise list of the conceptual properties defining the context of the
> working tree, index, and repository during normal use. This itemization
> would go far in explaining the synergies between the various commands. 

Speaking about "normal use"... I suggest you read about Git workflows:

$ git help gitworkflows

> 
> Functionally, all the commands merely manipulate these properties. If these
> properties were summarize in context one would expect that would represent a
> very complete functional model of Git. A user could review the description
> figure what they wanted to do and then find the command(s) to accomplish it.

It is like to say that driving a car merely means to manipulate its
components, so if these components were summarized, it would be all
that one needs to know to drive a car...

While I don't dispute that basic understanding of key Git concepts is
important, understanding of a typical Git workflow cannot be deduced
from knowledge of separate parts. Now if I were to describe Git just in
a few words, I would say that Git repository is just a DAG of objects,
the working tree is the place where you work, and the index is what
helps you to create fine-grained commits and do merges. But it says
very little (if anything) about how to use it.


Dmitry

  parent reply	other threads:[~2009-11-20  2:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 12:55 Hey - A Conceptual Simplication George Dennie
2009-11-18 13:18 ` Jonathan del Strother
2009-11-18 13:25 ` Jan Krüger
2009-11-18 18:51   ` George Dennie
2009-11-18 19:40     ` Jakub Narebski
2009-11-18 19:52       ` Jason Sewall
2009-11-19  2:03         ` George Dennie
2009-11-19  7:42           ` Björn Steinbrink
2009-11-19 20:12             ` George Dennie
2009-11-19 21:27               ` Junio C Hamano
2009-11-20  0:49               ` Jakub Narebski
2009-11-20  6:27                 ` Junio C Hamano
2009-11-20  2:31               ` Dmitry Potapov [this message]
2009-11-19 10:27           ` Jakub Narebski
2009-11-20  1:48           ` Dmitry Potapov
2009-11-20  1:55             ` david
2009-11-20  2:56               ` Dmitry Potapov
2009-11-20  2:35             ` Björn Steinbrink
2009-11-20  3:08               ` Dmitry Potapov
2009-11-20  1:35     ` Dmitry Potapov
2009-11-20  6:33       ` Junio C Hamano
2009-11-20 15:07         ` Dmitry Potapov
2009-11-18 13:30 ` Thomas Rast
2009-11-18 13:31 ` Jason Sewall
2009-11-18 20:36 ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091120023103.GC22556@dpotapov.dyndns.org \
    --to=dpotapov@gmail.com \
    --cc=B.Steinbrink@gmx.de \
    --cc=gdennie@pospeople.com \
    --cc=git@vger.kernel.org \
    --cc=jasonsewall@gmail.com \
    --cc=jk@jk.gs \
    --cc=jnareb@gmail.com \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).