From: Junio C Hamano <gitster@pobox.com>
To: "Julia Evans" <julia@jvns.ca>
Cc: "Julia Evans" <gitgitgadget@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 0/3] [doc] Remove gittutorial-2
Date: Wed, 30 Sep 2026 00:50:14 -0700 [thread overview]
Message-ID: <xmqqzewzch55.fsf@gitster.g> (raw)
In-Reply-To: <8a5b742a-3f11-4bfa-954b-ffdd839b6d43@app.fastmail.com> (Julia Evans's message of "Tue, 29 Sep 2026 06:42:40 -0400")
"Julia Evans" <julia@jvns.ca> writes:
>> So I personally feel it is OK to remove the old one, without
>> promising or even hinting at what in the new one that replaces it.
>> But we would want to see its replacement in the not-so-distant
>> future.
>
> I'm not planning to replace gittutorial-2 since the material in it
> is already covered by gitdatamodel and gitcore-tutorial.
OK. I didn't sense that from the proposed log messages for these
patches. Sorry for my misunderstanding.
>> Also, we may want to decide what to do with gittutorial. It is
>> short and reasonably sweet. One old-fashioned thing that does not
>> exactly match today's prevalent usage patterns may be that it starts
>> tracking a new project from a tarball, but other than that, it may
>> not hurt to keep it around. I do not know.
>
> We definitely want a tutorial that covers `git init`, `git add`, `git commit`,
> etc. Any replacement would definitely cover those topics, but
> I don't see the value of having 2 such tutorials.
> Why do you think it would be valuable to keep it around? It seems
> like it would cause a lot of confusion to me.
You confuse me.
What do you mean by "it" in "keep it around"? gittutorial.adoc?
If so you said it yourself, that we want to have a tutorial that
covers the basics like `git init` etc.
Or do you mean some other document, like gittutorial-2? It would
have made sense to keep it while a replacement was being written, to
make comparison easier, *if* the goal were to make sure that the new
one covers everything the existing one covered, but we already
agreed that it is not the goal to salvage what is in gittutorial-2
(and that is why I personally feel it is OK to remove the old one
first).
Puzzled.
next prev parent reply other threads:[~2026-09-30 7:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 20:25 [PATCH 0/3] [doc] Remove gittutorial-2 Julia Evans via GitGitGadget
2026-09-28 20:25 ` [PATCH 1/3] " Julia Evans via GitGitGadget
2026-09-28 20:25 ` [PATCH 2/3] [doc] Remove references to gittutorial-2 Julia Evans via GitGitGadget
2026-09-28 20:25 ` [PATCH 3/3] [doc] Delete translations of gittutorial-2 description Julia Evans via GitGitGadget
2026-09-29 7:50 ` [PATCH 0/3] [doc] Remove gittutorial-2 Junio C Hamano
2026-09-29 10:42 ` Julia Evans
2026-09-29 11:09 ` Julia Evans
2026-09-30 7:50 ` Junio C Hamano [this message]
2026-10-01 22:21 ` Julia Evans
2026-10-02 7:38 ` Junio C Hamano
2026-09-29 21:58 ` Junio C Hamano
2026-09-29 22:24 ` Junio C Hamano
2026-09-30 6:15 ` Tuomas Ahola
2026-09-30 14:22 ` Junio C Hamano
2026-09-30 13:16 ` Julia Evans
2026-09-30 14:07 ` Kristoffer Haugsbakk
2026-09-30 6:00 ` Tuomas Ahola
2026-09-30 14:01 ` Julia Evans
2026-10-05 20:20 ` [PATCH v2 0/2] " Julia Evans via GitGitGadget
2026-10-05 20:20 ` [PATCH v2 1/2] doc: remove gittutorial-2 Julia Evans via GitGitGadget
2026-10-05 20:37 ` Kristoffer Haugsbakk
2026-10-05 20:20 ` [PATCH v2 2/2] doc: remove references to gittutorial-2 Julia Evans via GitGitGadget
2026-10-05 20:37 ` [PATCH v2 0/2] [doc] Remove gittutorial-2 Junio C Hamano
2026-10-06 5:50 ` Tuomas Ahola
2026-10-06 17:17 ` Junio C Hamano
2026-10-06 18:45 ` Tuomas Ahola
2026-10-06 20:48 ` Junio C Hamano
2026-10-06 17:34 ` Julia Evans
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=xmqqzewzch55.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