From: Keshav Kini <keshav.kini@gmail.com>
To: git@vger.kernel.org
Subject: Re: Command-line git Vs IDE+plugin?
Date: Tue, 19 Nov 2013 10:55:10 -0600 [thread overview]
Message-ID: <871u2cpc0h.fsf@gmail.com> (raw)
In-Reply-To: 201311191336.31000.thomas@koch.ro
Thomas Koch <thomas@koch.ro> writes:
> But also from experience I can tell that without exception everybody whom I
> teached Git understood it only after being introduced to the basic concepts of
> Git and how to inspect and operate them on the commandline. Others told me
> from similar experiences.
>
> Those concepts are:
>
> - hashes
> - content adressable storage
> - blops being referenced by trees being referenced by commits
A great reference I always point people to for exactly those reasons is
Sitaram Chamarty's "git concepts simplified":
http://gitolite.com/gcs/
-Keshav
next prev parent reply other threads:[~2013-11-19 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 17:11 Command-line git Vs IDE+plugin? Matthieu Moy
2013-11-18 17:42 ` Philippe Vaucher
2013-11-18 18:46 ` Matthieu Moy
2013-11-19 9:53 ` Konstantin Khomoutov
2013-11-18 17:47 ` Andreas Krey
2013-11-19 12:36 ` Thomas Koch
2013-11-19 16:53 ` Junio C Hamano
2013-11-19 17:20 ` Matthieu Moy
2013-12-04 9:56 ` Gauthier Östervall
2013-11-19 16:55 ` Keshav Kini [this message]
2013-11-19 12:45 ` Noufal Ibrahim KV
2013-12-04 11:10 ` Chris Packham
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=871u2cpc0h.fsf@gmail.com \
--to=keshav.kini@gmail.com \
--cc=git@vger.kernel.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).