GNU bug report logs - #58336
[PATCH] HACKING: allow backward compatibilities again

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 58336 in the body.
You can then email your comments to 58336 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Kelvin M. Klann" <kmk3.code <at> protonmail.com>
To: "automake-patches <at> gnu.org" <automake-patches <at> gnu.org>,
 Karl Berry <karl <at> freefriends.org>
Subject: [PATCH] HACKING: allow backward compatibilities again
Date: Thu, 06 Oct 2022 13:02:45 +0000

See commit v1.16.3-20-g0c8100cb6 ("doc: HACKING updates.", 2021-05-12).

Copyright-paperwork-exempt: yes
---
 HACKING | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/HACKING b/HACKING
index 248fd4b03..88d5274a9 100644
--- a/HACKING
+++ b/HACKING
@@ -174,7 +174,7 @@
 * Major releases can introduce backward-incompatibilities (albeit such
   incompatibilities should be announced well in advance, and a smooth
   transition plan prepared for them), and try more risky and daring
-  refactorings and code cleanups.  Still, backward compatibilities are
+  refactorings and code cleanups.  Still, backward incompatibilities are
   extremely undesirable and should be avoided at all costs.

 * For more information, refer to the extensive discussion associated
--
2.38.0

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Karl Berry <karl <at> freefriends.org>
To: kmk3.code <at> protonmail.com
Cc: automake-patches <at> gnu.org
Subject: Re: [PATCH] HACKING: allow backward compatibilities again
Date: Thu, 6 Oct 2022 15:10:55 -0600

    Subject: [PATCH] HACKING: allow backward compatibilities again

:)

Thanks, I applied the fix.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.