git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "C. Scott Ananian" <cscott@laptop.org>
To: "Michael J Gruber" <git@drmicha.warpmail.net>
Cc: "David Howells" <dhowells@redhat.com>,
	git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Simplified GIT usage guide
Date: Fri, 19 Dec 2008 12:08:22 -0500	[thread overview]
Message-ID: <c6d9bea0812190908k223b6156j238763baeda8a0b7@mail.gmail.com> (raw)
In-Reply-To: <494B68B8.20107@drmicha.warpmail.net>

On Fri, Dec 19, 2008 at 4:26 AM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> C. Scott Ananian venit, vidit, dixit 19.12.2008 01:47:
>> On Fri, Dec 12, 2008 at 1:28 PM, David Howells <dhowells@redhat.com> wrote:
>>> Add a guide to using GIT's simpler features.
>>> diff --git a/Documentation/git-haters-guide.txt b/Documentation/git-haters-guide.txt
>>> +In the above example, I've assumed that you've got your own tree with the head
>>> +at commit C3, and that you've got a branch that you want to merge, which has
>>> +its head at commit B3.  After merging them, you'd end up with a directed,
>>> +cyclic tree:
>>
>> That should be, "acyclic".  There are no cycles, because the graph is directed.
>
> Well, directed graphs can have cycles. But the revision graph of a
> revision control system has to be an acyclic directed graph. Otherwise
> parenthood would be a complicated matter ;)

I mean that the example given didn't have a cycle (even though it has
nodes arranged in a circle) because of the orientation of the edges.
But you're right, "directed acyclic graph" is a better correction; the
nodes in git do not form a tree.
 --scott

-- 
                         ( http://cscott.net/ )

      reply	other threads:[~2008-12-19 17:09 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
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 [this message]

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=c6d9bea0812190908k223b6156j238763baeda8a0b7@mail.gmail.com \
    --to=cscott@laptop.org \
    --cc=dhowells@redhat.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@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).