From: Junio C Hamano <gitster@pobox.com>
To: "Julia Evans" <julia@jvns.ca>
Cc: git@vger.kernel.org
Subject: Re: Rewriting the Git tutorial to cover less content
Date: Fri, 25 Sep 2026 09:47:41 -0700 [thread overview]
Message-ID: <xmqq7bk9wa4y.fsf@gitster.g> (raw)
In-Reply-To: <bd5d9451-ac5a-4274-9a7a-57ae99864fe9@app.fastmail.com> (Julia Evans's message of "Fri, 25 Sep 2026 12:08:51 -0400")
"Julia Evans" <julia@jvns.ca> writes:
> I'm working on a patch series to replace `gittutorial.adoc` with a completely
> rewritten tutorial, since a lot has changed since it was originally written.
> ...
> I'm excited about this direction, I've already gotten some positive feedback from
> test readers, like:
>
>> I can say I liked this tutorial better than any of the other git tutorials I've tried.
>
> and
>
>> I really like the tutorial, it's easy to follow and I learned a lot!
>
> I have some ideas for what to do with `gittutorial-2` too but I'll leave
> that for another discussion.
As long as it does not mean that learners now have to read three
documents instead of two (i.e., your replacement, gittutorial.adoc,
and gittutorial-2.adoc), I am also excited.
Omitting some material that is covered in the current tutorial from
the new one would mean that the topics covered by the remainder of
the current tutorial have to be sifted into three buckets: one that
is to be discarded because it is no longer useful to the target
audience, another that needs to be described somewhere in our
documentation set, and the rest that need to be taught elsewhere,
though that may be beyond the scope of the project documentation
and better left to other projects that produce "books on Git". It
is somewhat unclear from your description what your plan is to cover
other topics that should still be taught.
As we reached consensus at the contributors' summit, we should wean
ourselves away from the mindset that these tutorial materials can be
incrementally polished to match today's needs, so if the plan for
'the rest' is also to write on these topics from the ground up, that
would be very good.
Thanks.
next prev parent reply other threads:[~2026-09-25 16:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 19:29 [PATCH] doc: add more AsciiDoc cross-references Julia Evans via GitGitGadget
2026-09-22 20:20 ` Junio C Hamano
2026-09-22 20:54 ` Julia Evans
2026-09-23 21:40 ` Jeff King
2026-09-24 12:30 ` Julia Evans
2026-09-24 15:55 ` Jeff King
2026-09-24 17:15 ` Junio C Hamano
2026-09-24 17:22 ` Julia Evans
2026-09-24 18:17 ` Junio C Hamano
2026-09-24 18:42 ` Jeff King
2026-09-23 19:06 ` Kristoffer Haugsbakk
2026-09-23 22:00 ` Jeff King
2026-09-25 0:52 ` [PATCH v2] " Julia Evans via GitGitGadget
2026-09-25 8:27 ` Jeff King
2026-09-25 16:08 ` Rewriting the Git tutorial to cover less content Julia Evans
2026-09-25 16:47 ` Junio C Hamano [this message]
2026-09-25 17:25 ` Julia Evans
2026-09-25 18:23 ` Junio C Hamano
2026-09-25 19:22 ` Julia Evans
2026-09-25 19:34 ` Junio C Hamano
2026-09-28 12:21 ` Julia Evans
2026-09-28 15:16 ` 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=xmqq7bk9wa4y.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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