From 1bcc3473d764beb30159612501d957ebdca84487 Mon Sep 17 00:00:00 2001 From: Tom van Woudenberg Date: Mon, 24 Feb 2025 21:34:32 +0100 Subject: [PATCH] WIP --- book/installation-and-setup/versioning_archived.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/installation-and-setup/versioning_archived.md b/book/installation-and-setup/versioning_archived.md index 94e54b3..af3899f 100644 --- a/book/installation-and-setup/versioning_archived.md +++ b/book/installation-and-setup/versioning_archived.md @@ -1,5 +1,5 @@ # Keep source code and website of all versions -Although you might only want to share the most recent version of the book with your readers, it might be useful too the have the source code of those versions somewhere too. Don't be afraid, git makes it very easy to make this possible. +In case you'd like other to use your source code and you've different versions, it might be useful to have the source code of those versions somewhere too. Don't be afraid, git makes it very easy to make this possible. Git allows you to go back in the git history to the source code of old versions. To make this as easy as possible for readers, use branches, tags and releases instead of having the readers scroll through a long list of (not alway very descriptive) commit descriptions. How to use tags and releases is described in [](./versioning_changelog.md) \ No newline at end of file