From 7450a8cfa3768cf0992bfdf02686dedb5acadf91 Mon Sep 17 00:00:00 2001 From: David Christiansen Date: Tue, 10 Oct 2023 22:13:05 +0200 Subject: [PATCH] doc: describe commit conventions for update-stage0 Updates to stage0 should be their own commits. --- doc/dev/bootstrap.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/dev/bootstrap.md b/doc/dev/bootstrap.md index 3fb2ad2411..5ee9ff0c18 100644 --- a/doc/dev/bootstrap.md +++ b/doc/dev/bootstrap.md @@ -69,6 +69,13 @@ Finally, when we want to use new language features in the library, we need to update the stage 0 compiler, which can be done via `make -C stageN update-stage0`. `make update-stage0` without `-C` defaults to stage1. +Updates to `stage0` should be their own commits in the Git history. In +other words, before running `make update-stage0`, please commit your +work. Then, commit the updated `stage0` compiler code with the commit message: +``` +chore: update stage0 +``` + ## Further Bootstrapping Complications As written above, changes in meta code in the current stage usually will only