From: "Ping Yin" <pkufranky@gmail.com>
To: "Nick Andrew" <nick@nick-andrew.net>
Cc: "David Howells" <dhowells@redhat.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
torvalds@osdl.org, git@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Miklos Vajna" <vmiklos@frugalware.org>
Subject: Re: [PATCH] Simplified GIT usage guide
Date: Sun, 14 Dec 2008 09:45:49 +0800 [thread overview]
Message-ID: <46dff0320812131745h3d30738ajf704a4336f5dec40@mail.gmail.com> (raw)
In-Reply-To: <20081213230504.GA21912@mail.local.tull.net>
On Sun, Dec 14, 2008 at 7:05 AM, Nick Andrew <nick@nick-andrew.net> wrote:
> The way I did it was to start with the directed acyclic graph of
> commits, explaining how branches fork the graph and merges join
> it. This was presented to people who know subversion, and so they
> immediately became aware that there are other ways to manage source
> code than in a linear r1 r2 r3 r4 r5. I described tags and branch
> heads briefly.
>
> Next up I described the things you'd do with git: add new commits,
> create a branch, merge a branch, rebase, tag, push and fetch and
> showed what that does with the dag of commits.
>
> Finally I showed the actual commands used to perform those actions.
> I didn't get into the object database structure at all (that was
> prepared in case I had extra time).
>
I think this is the right way to start with the DAG. And i do the same.
next prev parent reply other threads:[~2008-12-14 1:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 18:28 [PATCH] Simplified GIT usage guide David Howells
2008-12-12 18:53 ` Miklos Vajna
2008-12-12 18:57 ` Johannes Schindelin
2008-12-19 0:02 ` Paul E. McKenney
2008-12-19 0:28 ` Junio C Hamano
2008-12-19 1:27 ` Paul E. McKenney
2008-12-24 4:35 ` Valdis.Kletnieks
2008-12-19 2:38 ` Johannes Schindelin
2008-12-19 5:25 ` Paul E. McKenney
2008-12-12 19:02 ` David Howells
2008-12-12 19:09 ` Miklos Vajna
2008-12-13 1:12 ` David Howells
2008-12-13 3:34 ` Miklos Vajna
2008-12-12 19:12 ` David Howells
2008-12-12 19:24 ` Sverre Rabbelier
2008-12-12 19:40 ` Aidan Van Dyk
2008-12-13 23:05 ` Nick Andrew
2008-12-14 1:45 ` Ping Yin [this message]
2008-12-12 19:39 ` Jakub Narebski
2008-12-12 19:47 ` J. Bruce Fields
2008-12-13 1:03 ` J. Bruce Fields
2008-12-13 1:14 ` David Howells
2008-12-12 20:00 ` Jeff Garzik
2008-12-12 21:34 ` Chris Friesen
2008-12-13 5:59 ` Junio C Hamano
2008-12-13 23:12 ` Nick Andrew
2008-12-12 20:07 ` Nicolas Pitre
2008-12-13 0:30 ` David Howells
2008-12-13 1:04 ` David Howells
2008-12-13 1:16 ` Sverre Rabbelier
2008-12-19 6:33 ` Willy Tarreau
2008-12-13 1:22 ` Nicolas Pitre
2008-12-13 3:35 ` Junio C Hamano
2008-12-14 10:33 ` Matthieu Moy
2008-12-14 17:33 ` Marcin Slusarz
2008-12-19 0:47 ` C. Scott Ananian
2008-12-19 9:26 ` Michael J Gruber
2008-12-19 17:08 ` C. Scott Ananian
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=46dff0320812131745h3d30738ajf704a4336f5dec40@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=dhowells@redhat.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@nick-andrew.net \
--cc=torvalds@osdl.org \
--cc=vmiklos@frugalware.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).