Update HACKING.

Suggested by Paul Eggert in
<https://lists.gnu.org/archive/html/bug-gnulib/2024-04/msg00388.html>.

* HACKING: Mention an alternative to gitk.

diff --git a/ChangeLog b/ChangeLog
index d2c82d41ccfeb8a107f48b7b324d7804c6853ac6..58c7306f1587ae3298ea2fd106b3e940e7ece6d5 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2024-04-23  Bruno Haible  <bruno@clisp.org>
+
+       Update HACKING.
+       Suggested by Paul Eggert in
+       <https://lists.gnu.org/archive/html/bug-gnulib/2024-04/msg00388.html>.
+       * HACKING: Mention an alternative to gitk.
+
 2024-04-23  Collin Funk  <collin.funk1@gmail.com>
 
        gnulib-tool.py: Make better use of imports.

diff --git a/HACKING b/HACKING
index 7a23a339821c1be54efacb52d2699416f8bd70d0..8ffe5d5f5e42f28d05b332d7e93451b75d470b03 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -18,8 +18,13 @@ Using git
   recommended that you configure git with 'git config pull.rebase = true'.
 
 * Before pushing a commit, it is highly recommended that you review it in
-  its entirety. The easiest way to do so is to run
-    $ gitk
+  its entirety. The easiest ways to do so are
+    * to run
+        $ git format-patch -1
+      and then read the patch in an editor that has syntax-colouring of patch
+      files, or
+    * to run
+        $ gitk
 
 * We update the ChangeLog by hand.  The commit message is usually identical
   to the ChangeLog entry, with the date and author line removed, with