automake-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[automake-commit] branch master updated: doc: typo in HACKING changes.


From: Karl Berry
Subject: [automake-commit] branch master updated: doc: typo in HACKING changes.
Date: Thu, 06 Oct 2022 17:09:06 -0400

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

karl pushed a commit to branch master
in repository automake.

View the commit online:
https://git.savannah.gnu.org/gitweb/?p=automake.git;a=commitdiff;h=63216e554ffcc7ae2fb451fcc89c582dca20088e

The following commit(s) were added to refs/heads/master by this push:
     new 63216e554 doc: typo in HACKING changes.
63216e554 is described below

commit 63216e554ffcc7ae2fb451fcc89c582dca20088e
Author: Kelvin M. Klann <kmk3.code@protonmail.com>
AuthorDate: Thu Oct 6 14:08:55 2022 -0700

    doc: typo in HACKING changes.
    
    * HACKING: allow backward compatibilities again.
---
 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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]