Re: emacs-30 21be5cadaf1: ; * lisp/subr.el (sha1): Fix typo in docstring.

Re: emacs-30 21be5cadaf1: ; * lisp/subr.el (sha1): Fix typo in docstring.

[Pip Cet]

Ulrich Müller <ulm@gentoo.org> writes:

> branch: emacs-30
> commit 21be5cadaf1e43cf886f38cb14fa25b96d8b551d
> Author: Ulrich Müller <ulm@gentoo.org>
> Commit: Ulrich Müller <ulm@gentoo.org>
>
>     ; * lisp/subr.el (sha1): Fix typo in docstring.
> ---
>  lisp/subr.el | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lisp/subr.el b/lisp/subr.el
> index 31c53a6455b..a8e3df14cd3 100644
> --- a/lisp/subr.el
> +++ b/lisp/subr.el
> @@ -4482,7 +4482,7 @@ Otherwise, return nil."
>  OBJECT is either a string or a buffer.  Optional arguments START and
>  END are character positions specifying which portion of OBJECT for
>  computing the hash.  If BINARY is non-nil, return a 40-byte unibyte
> -string; otherwise returna 40-character string.
> +string; otherwise return a 40-character string.

In my case, if BINARY is non-nil, a 20-byte unibyte string is returned,
which matches the 160 bits SHA-1 actually produces. Okay to fix that on
emacs-30, too?

Pip

Re: emacs-30 21be5cadaf1: ; * lisp/subr.el (sha1): Fix typo in docstring.

[Stefan Kangas]

Pip Cet <pipcet@protonmail.com> writes:

> In my case, if BINARY is non-nil, a 20-byte unibyte string is returned,
> which matches the 160 bits SHA-1 actually produces. Okay to fix that on
> emacs-30, too?

Doc fixes are okay on emacs-30, yes.