Re: Rewriting the Git tutorial to cover less content
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 25, 2026, 18:23 UTC
- Message-ID
- <xmqqh5jdur4c.fsf@gitster.g>
- In-Reply-To
- <4c9f0480-768a-48ba-9753-b4d34188b1a1@app.fastmail.com>
"Julia Evans" <julia@jvns.ca> writes:
Show 5 quoted lines
>> See gittutorial(7) to get started, then see giteveryday(7) for >> a useful minimum set of commands. > > This is a nice friendly statement, but in my opinion `gittutorial` and > `giteveryday` really do not live up to what it promises, ...
Yes, it outlived its time and the world has moved on.
Show 8 quoted lines
> I see a couple of possible strategies. > > * We can write new guides which are clearer > * We can link to outside resources (via https://git-scm.com/learn) > which we think do a good job. Right now that page is pretty > out of date and it would be very easy to improve. > > I think a mix of both is probably most realistic right now.
Whatever we do, it is not enough that new guides are more clear than the current one. The goal should be that it also is sufficient to replace the current one. Removing the stale and unuseful document can be made the primary goal, and a new document may be a means to do so ;-).
I do not know if we have bandwidth to keep external links fresh, and having a set of links to stale pages ourselves may hurt more than help.
Thanks.