Re: Rewriting the Git tutorial to cover less content
- From
Julia Evans <julia@jvns.ca>
- Date
- Sep 28, 2026, 12:21 UTC
- Message-ID
- <7004c3b1-2100-4a90-9815-2a679ceb25b2@app.fastmail.com>
- In-Reply-To
- <xmqqv77tt9a4.fsf@gitster.g>
Show 5 quoted lines
> Dealing with broken links is easier as we can just remove them. > Noticing a link that points at an unmaintained stale document that > describes what used to be relevant but no longer in today's > environment and replacing it with something more relevant was what I > am worried about.
Thanks, this is helpful. Let me try to rephrase to see if I understand, let me know if I'm understanding wrong.
When possible, it's better to split up changes into smaller pieces so that they can be reviewed more easily.
For this change, it would help to split it up into two different patch series: "remove tutorial" and "add new tutorial", where the first patch series deletes all references to the tutorial. If we do it this way, we can both make sure that there isn't any content that we regret deleting, and lets us take a look at the documents that reference the tutorial too.
- Julia