git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Mark Lodato <lodatom@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: A Visual Git Reference
Date: Wed, 10 Feb 2010 00:20:57 -0500	[thread overview]
Message-ID: <20100210052057.GE28526@coredump.intra.peff.net> (raw)
In-Reply-To: <ca433831002081134m698f531bwa22f0474db0cdcb@mail.gmail.com>

On Mon, Feb 08, 2010 at 02:34:21PM -0500, Mark Lodato wrote:

> I put together a "Visual Git Reference" containing visualizations of
> the most common git commands, for people who prefer to see images over
> text.  It is designed as a reference, not a tutorial, so readers need
> to have some amount of experience before the page will become useful.
> 
> URL: http://marklodato.github.com/visual-git-guide/
> Git repo: http://github.com/marklodato/visual-git-guide/
> 
> If you have any feedback or suggestions, please let me know!

This looks really awesome, thanks for doing it (though I'll admit I
threw up in my mouth a little when I saw you did all of the diagrams as
TeX. ;) ).

One of the projects I have wanted to do but never found time for is a
"Git Picture Glossary". I was intending to start with much simpler
concepts, like how the various object types relate, what a ref is, how a
symref differs, what a detached HEAD is, etc. And then move on to "here
is what happens when you branch", "here is what happens when you merge",
etc. Sort of like "Git for Computer Scientists", but organized as a
glossary, with each entry starting off with "to understand this, you
first need to understand entries X and Y", with links.

And it seems like what you have done is more or less the same thing,
except you skipped all of the really basic entries and went straight to
the action-oriented ones.

-Peff

  parent reply	other threads:[~2010-02-10  5:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08 19:34 A Visual Git Reference Mark Lodato
2010-02-08 19:51 ` Peter Baumann
2010-02-08 20:21   ` Mark Lodato
2010-02-08 20:34     ` Jon Seymour
2010-02-08 20:57       ` Mark Lodato
2010-02-09  0:09     ` Johannes Schindelin
2010-02-08 21:57 ` Daniel Barkalow
2010-02-09  0:18   ` Mark Lodato
2010-02-10  3:40   ` John J. Franey
2010-02-10  5:20 ` Jeff King [this message]
2010-03-17 19:03   ` Scott R. Godin
2010-02-10 17:02 ` Dilip M
2010-02-18  1:17 ` Michael Witten
2010-02-18  1:39   ` Jeff King
2010-02-18  1:39   ` Mark Lodato
2010-02-18  3:03     ` Michael Witten
2010-02-18 12:38     ` Tor Arvid Lund
2010-02-18 12:53     ` Tay Ray Chuan

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=20100210052057.GE28526@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=lodatom@gmail.com \
    /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).