git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Documentation/tutorial: misc updates

From
Junio C Hamano <junkio@cox.net>
Date
Jan 3, 2007, 16:24 UTC
Message-ID
<7vejqcoz7s.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<8aa486160701030609g22eadf0brf8743dad5701f315@mail.gmail.com>
"Santi Béjar" <sbejar@gmail.com> writes:
Show 13 quoted lines
> On 1/3/07, Horst H. von Brand <vonbrand@inf.utfsm.cl> wrote:
>> Santi Béjar <sbejar@gmail.com> wrote:
>> >
>> > -Every commit has at least one "parent" commit, which points to the
>> > -previous state of the project:
>> > +Every commit has at least one "parent" commit (except the first),
>> > +which points to the previous state of the project:
>>
>> And how can it have more than one parent? If you mention it, better come
>> clean about merges (can be explained in detail later).
>
> I have not mentined it, I've just added the exception that the
> firt/root commits have zero parents.
Well, it does not matter who originally is at fault ;-).
Let's just do this.
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
index f0a5526..0cc234f 100644
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -400,7 +400,7 @@ $ git show HEAD		# the tip of the current branch
 $ git show experimental	# the tip of the "experimental" branch
 -------------------------------------
 
-Every commit has at least one "parent" commit (except the first),
+Every commit usually has one "parent" commit
 which points to the previous state of the project:
 
 -------------------------------------

After this paragraph, we say "merge has more than one", so it's
all consistent and presented in the right order.  By the time
the reader starts wondering about the initial commit, we've
shown the use of HEAD^^^^ and HEAD~$n enough that the reader can
experiment on his/her own.
Previous: Santi BéjarNext: Santi Béjar
Message 4 of 5 in “Re: [PATCH] Documentation/tutorial: misc updates”
  1. Horst H. von BrandJan 3, 2007
  2. Jakub NarebskiJan 3, 2007
  3. Santi BéjarJan 3, 2007
  4. Junio C HamanoJan 3, 2007
  5. Santi BéjarJan 3, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.