From 29b336bb8de6f40635a4364b46f915215450ce2c Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 31 Aug 2026 03:22:24 +0200 Subject: [PATCH] Say the remedy beside the problem in status MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A status that names what is wrong and not what to do about it makes somebody go and find the command — and the command is the whole point of having noticed. The hint existed on one of the two paths that print this. --- cmd/mesh-control/main.go | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/cmd/mesh-control/main.go b/cmd/mesh-control/main.go index a1f218a..08b4add 100644 --- a/cmd/mesh-control/main.go +++ b/cmd/mesh-control/main.go @@ -1880,6 +1880,10 @@ func statusCommand(ctx context.Context, args []string) error { fmt.Printf(" %-18s assigned to nothing\n", "") } } + // The remedy, beside the problem. A status that says what is wrong and not what to do + // about it makes somebody go and find the command, and the command is the whole point of + // having noticed. + fmt.Printf("\n `build --behind` builds them; `push --behind` sends them on\n") fmt.Println() }