From 0df626b829ae9f2e0ddcc2378f924d77622bfbb1 Mon Sep 17 00:00:00 2001
From: Brad House <brad@brad-house.com>
Date: Wed, 24 Jul 2024 05:48:03 -0400
Subject: [PATCH] release procedure: make commands cut and paste-able as a
 whole

---
 RELEASE-PROCEDURE.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/RELEASE-PROCEDURE.md b/RELEASE-PROCEDURE.md
index 3cba9acb..c686a9f9 100644
--- a/RELEASE-PROCEDURE.md
+++ b/RELEASE-PROCEDURE.md
@@ -18,10 +18,10 @@ in the source code repo
   branch like:
 ```
 BRANCH=1.32
-git pull
-git checkout main
-git checkout -b v${BRANCH} main
-git commit --allow-empty -m "Created release branch v${BRANCH}"
+git pull && \
+git checkout main && \
+git checkout -b v${BRANCH} main && \
+git commit --allow-empty -m "Created release branch v${BRANCH}" && \
 git push -u origin v${BRANCH}
 ```
 - make sure all relevant changes are committed on the release branch
@@ -31,9 +31,9 @@ git push -u origin v${BRANCH}
 ```
 BRANCH=1.32
 RELEASE=1.32.0
-git checkout v${BRANCH}
-git pull
-git tag -s v${RELEASE} -m 'c-ares release v${RELEASE}' v${BRANCH}
+git checkout v${BRANCH} && \
+git pull && \
+git tag -s v${RELEASE} -m 'c-ares release v${RELEASE}' v${BRANCH} && \
 git push origin --tags
 ```
 - Create the release tarball using `make dist`, it is best to check out the