Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Julia Evans <julia@jvns.ca>
Cc: Julia Evans via GitGitGadget <gitgitgadget@gmail.com>,
	 git@vger.kernel.org
Subject: Re: [PATCH 2/2] doc: add new Git tutorial for beginners
Date: Tue, 20 Oct 2026 12:13:15 -0700	[thread overview]
Message-ID: <xmqqjyncuqwk.fsf@gitster.g> (raw)
In-Reply-To: <xmqq1p9kw6qu.fsf@gitster.g> (Junio C. Hamano's message of "Tue, 20 Oct 2026 11:45:45 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> Junio C Hamano <gitster@pobox.com> writes:
>
>> Julia Evans <julia@jvns.ca> writes:
>>
>>>> The goal is well described, and overall the tutorial is well-paced
>>>> and avoids common beginner traps.  Since Ben has covered the text
>>>> fairly well, the remainder of this message has just some leftover
>>>> nitpicks.
>>
>> My local build of 'seen' just saw these:
>>
>> gittutorial.adoc:124: section delimiter not preceded by an empty line
>> gittutorial.adoc:487: section delimiter not preceded by an empty line
>>
>> I haven't checked what these two lines contain yet.
>
> Now I have.  It was the underline-hyphen thing.  The earlier one is
> for Step 3. I missed, and the later one is what I pointed out in the
> nitpick.

Regarding the topic in your other message, this discussion helps us
contrast the two styles offered by AsciiDoc.

The Atx-style headers, e.g.,

 = This is a first level header
 == this is a second level header

free us from the need to count characters for Setext-style
headers, e.g.,

 This is a first level header
 ============================
 This is a second level header
 -----------------------------

Besides, counting characters becomes tricky once we step outside
US-ASCII anyway, which is another reason to prefer the modern
Atx-style prefix format.

I find it somewhat harder to notice when a section is at the
wrong level in a document using Atx-style headers.  With
Setext-style, the long underline makes mismatches stand out;
indeed, that is how I caught a handful of mistakes over the
course of this project that I suspect I otherwise wouldn't have
found.  Once found, however, such a mistake is easier to
correct.


  reply	other threads:[~2026-10-20 19:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 19:37 [PATCH 0/2] WIP: doc: add new git tutorial Julia Evans via GitGitGadget
2026-10-06 19:37 ` [PATCH 1/2] doc: remove gittutorial Julia Evans via GitGitGadget
2026-10-06 19:37 ` [PATCH 2/2] doc: add new Git tutorial for beginners Julia Evans via GitGitGadget
2026-10-07 19:48   ` D. Ben Knoble
2026-10-19 14:24     ` Julia Evans
2026-10-19 16:49       ` Ben Knoble
2026-10-19 20:42         ` Julia Evans
2026-10-19 21:14           ` D. Ben Knoble
2026-10-20 17:11   ` Junio C Hamano
2026-10-20 17:59     ` Julia Evans
2026-10-20 18:26       ` Junio C Hamano
2026-10-20 18:27       ` Junio C Hamano
2026-10-20 18:45         ` Junio C Hamano
2026-10-20 19:13           ` Junio C Hamano [this message]
2026-10-20 18:22     ` Julia Evans
2026-10-20 18:30       ` Junio C Hamano
2026-10-07 19:26 ` [PATCH 0/2] WIP: doc: add new git tutorial D. Ben Knoble
2026-10-19 14:55 ` [PATCH v2 0/2] " Julia Evans via GitGitGadget
2026-10-19 14:55   ` [PATCH v2 1/2] doc: remove gittutorial Julia Evans via GitGitGadget
2026-10-19 14:55   ` [PATCH v2 2/2] doc: add new Git tutorial for beginners Julia Evans via GitGitGadget
2026-10-20  1:24   ` [PATCH v2 0/2] doc: add new git tutorial Junio C Hamano
2026-10-20  2:24     ` Ben Knoble
2026-10-20 12:18       ` Julia Evans
2026-10-20 18:50         ` Tuomas Ahola
2026-10-20 19:13     ` Junio C Hamano

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=xmqqjyncuqwk.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=julia@jvns.ca \
    /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