From 5c8a37e9b6174dd42baf8cca24d4fcff6d2da7d8 Mon Sep 17 00:00:00 2001
From: Stefan Kangas <stefankangas@gmail.com>
Date: Fri, 28 Feb 2025 05:21:48 +0100
Subject: [PATCH] Recommend secure-hash in md5 docstring

* src/fns.c (Fmd5): Repeat explanation from manual about md5 being
"semi-obsolete", and recommend using secure-hash instead.

(cherry picked from commit 6f5c322f5974786290b1b3e68b5a0685ddec3410)
---
 src/fns.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/src/fns.c b/src/fns.c
index 4e00ad71c2e..d289af22cd8 100644
--- a/src/fns.c
+++ b/src/fns.c
@@ -6374,6 +6374,11 @@ command `prefer-coding-system') is used.
 If NOERROR is non-nil, silently assume the `raw-text' coding if the
 guesswork fails.  Normally, an error is signaled in such case.
 
+This function is semi-obsolete, since for most purposes it is equivalent
+to calling `secure-hash` with the symbol `md5' as the ALGORITHM
+argument.  The OBJECT, START and END arguments have the same meanings as
+in `secure-hash'.
+
 Note that MD5 is not collision resistant and should not be used for
 anything security-related.  See `secure-hash' for alternatives.  */)
   (Lisp_Object object, Lisp_Object start, Lisp_Object end, Lisp_Object coding_system, Lisp_Object noerror)
-- 
2.39.5