From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Leo <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Move sha1 to C?
Date: Sun, 22 May 2011 22:23:55 -0300 [thread overview]
Message-ID: <jwv7h9i9pqc.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m1pqnawlkz.fsf@th041140.ip.tsinghua.edu.cn> (Leo's message of "Mon, 23 May 2011 04:02:04 +0800")
> Do you mind if I do the following:
> 1. add sha1.[ch] from gnulib
> 2. export sha1 to elisp
> 3. obsolete sha1.el
Fine by me. 3 should also include "gut sha1.el's content" so that
loading it won't end up overwriting the C implementation with the old
Elisp code.
> Should the signature of sha1 stay as is or change to be similar to md5?
> (md5 OBJECT &optional START END CODING-SYSTEM NOERROR)
I don't have any opinion on this. The only thing I consider important
is to signal an error if the hashed text contains any
non-byte character.
Stefan
next prev parent reply other threads:[~2011-05-23 1:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 6:37 Move sha1 to C? Leo
2011-05-22 19:04 ` Stefan Monnier
2011-05-22 20:02 ` Leo
2011-05-23 1:23 ` Stefan Monnier [this message]
2011-05-23 8:44 ` Leo
2011-05-23 12:04 ` Stefan Monnier
2011-05-23 13:21 ` Leo
2011-05-23 13:27 ` Stefan Monnier
2011-05-23 13:34 ` Leo
2011-05-23 13:57 ` Stefan Monnier
2011-05-23 18:14 ` Leo
2011-05-23 19:15 ` Stefan Monnier
2011-05-23 22:10 ` Paul Eggert
2011-05-24 4:09 ` Leo
2011-05-24 10:01 ` Eli Zaretskii
2011-05-24 14:24 ` Leo
2011-05-24 22:01 ` Richard Stallman
2011-05-24 5:09 ` Thien-Thi Nguyen
2011-05-23 14:30 ` Eli Zaretskii
2011-05-23 17:47 ` Leo
2011-05-23 18:12 ` Eli Zaretskii
2011-05-23 18:23 ` Leo
2011-05-23 19:21 ` Eli Zaretskii
2011-05-23 7:21 ` Eli Zaretskii
2011-05-23 8:30 ` Leo
2011-05-23 15:27 ` Chong Yidong
2011-05-23 17:14 ` Leo
2011-05-23 17:38 ` Leo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv7h9i9pqc.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=sdl.web@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.