branch master updated: * README-hacking: git branch structure for after next release

[Gavin D. Smith]

This is an automated email from the git hooks/post-receive script.

gavin pushed a commit to branch master
in repository texinfo.

The following commit(s) were added to refs/heads/master by this push:
     new e37eee596a * README-hacking: git branch structure for after next 
release
e37eee596a is described below

commit e37eee596ad07f56c7a9989262db1e9c84b5a54f
Author: Gavin Smith <gavinsmith0123@gmail.com>
AuthorDate: Sat Sep 24 13:31:17 2022 +0100

    * README-hacking: git branch structure for after next release
---
 ChangeLog      | 4 ++++
 README-hacking | 3 +++
 2 files changed, 7 insertions(+)

diff --git a/ChangeLog b/ChangeLog
index 040b5f6d6c..ca962e6093 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2022-09-24  Gavin Smith  <gavinsmith0123@gmail.com>
+
+       * README-hacking: git branch structure for after next release
+
 2022-09-21  Gavin Smith  <gavinsmith0123@gmail.com>
 
        * doc/texinfo.tex (\image): Begin \vtop with negative kern by
diff --git a/README-hacking b/README-hacking
index d4e6088acc..213d9836db 100644
--- a/README-hacking
+++ b/README-hacking
@@ -337,6 +337,9 @@ until it's time to do pretests again.
 after next release:
 rename old ChangeLog and start a new one
 check TODO file and do pending tasks
+discuss on mailing list changing the git branch structure to allow quick
+  bug fix releases for severe bugs (e.g. glibc 2.34 incompatibility, info crash
+  in Brazillian Portuguese locale)
 delete these lines from README-hacking