From: Bruno Haible <bruno@clisp.org>
Date: Tue, 23 Apr 2024 19:26:20 +0000 (+0200)
Subject: Update HACKING.
X-Git-Tag: v1.0~14
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=875f8309a76e4916bf70d44ed0407a5edf95660f;p=thirdparty%2Fgnulib.git

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 d2c82d41cc..58c7306f15 100644
--- 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 7a23a33982..8ffe5d5f5e 100644
--- 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