Julia Evans's series deletes the existing Documentation/gittutorial.adoc, 671 lines, and adds a new tutorial in a second patch. The split is meant to make the patches easier to read on the list, since no old content is reused. The tutorial has two parts. Steps 1-7 create an empty repository and make two commits with git init, add, commit, status and diff. Steps 8-12 push to a host such as GitHub or GitLab with git remote add and git push.

The design notes say it introduces far fewer commands than the old tutorial so it can be finished in about an hour. It starts from an empty repository because many testers had no existing project or were intimidated by one. Evans reported 112 comments from 22 beta testers at the first posting and from about 30 later. Most finished it, and the most common request was for material on collaboration and branching. She has a draft branching tutorial but said it cannot fit in this series. She also said she might run out of funding if revisions take very long.

Reviewers D. Ben Knoble and Ben Knoble commented on command choices. They preferred "git config set" and pointed out that "git init <dir>" exists. Evans said she had not known about either. She said she wants the tutorial to work on older Git versions and to state which ones. She had claimed it works on "any version above 2.0" but had not checked that. Ben Knoble said he is happy with the mkdir-and-cd version and will go with whatever she settles on.

Part of the thread is about delivery. Junio C Hamano said he waited about 10 hours after seeing a cover letter and the patches never appeared in the list archive, and he asked whether GitGitGadget needed a nudge. Ben Knoble said he received the v2 patches and suspected the list or archive had dropped them, possibly because the messages were too big. Evans also said plain-text quoting makes it hard for her to see replies, and that she missed some.

The tutorial text itself has had little detailed review so far. Evans said she wants to avoid going through every detail yet because a second round of beta feedback is planned and the beginning will likely change.