From df361999a72ee5a05f58fd375f4c56b5cab5bf92 Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Mon, 29 Jun 2020 16:51:08 -0700
Subject: Update release advice

---
 HACKING | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/HACKING b/HACKING
index 615bb7ac..14ee274d 100644
--- a/HACKING
+++ b/HACKING
@@ -104,8 +104,7 @@ should check the results before committing them in git.
 
 ** Set the version number
 Update the version number in NEWS (with version, date, and release
-type) and ChangeLog, and mention in README whether the release is
-stable.  Make sure all changes are committed, then run `git tag -s -m
+type).  Make sure all changes are committed, then run `git tag -s -m
 <version> -u <gpg_key> v<version>'.  Do not push anything upstream at
 this point.
 
-- 
cgit v1.2.1