From: Ulrik Sverdrup <ulrik.sverdrup@gmail.com>
To: nico@cam.org
Cc: git@vger.kernel.org
Subject: Re: [PATCH] remove ARM and Mozilla SHA1 implementations
Date: Mon, 24 Aug 2009 13:42:08 +0200 [thread overview]
Message-ID: <a1b6cb1b0908240442t676a13a2ma706c489e3c06860@mail.gmail.com> (raw)
block-sha1/sha1.{ch} simply say this:
/*
* Based on the Mozilla SHA1 (see mozilla-sha1/sha1.c),
* optimized to do word accesses rather than byte accesses,
* and to avoid unnecessary copies into the context array.
*/
This means that if mozilla-sha1 is removed, we need to copy the
license information back to block-sha1.
Ulrik
next reply other threads:[~2009-08-24 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 11:42 Ulrik Sverdrup [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-17 23:56 [PATCH] remove ARM and Mozilla SHA1 implementations Nicolas Pitre
2009-08-18 0:09 ` Johannes Schindelin
2009-08-24 4:12 ` Nicolas Pitre
2009-08-24 11:33 ` Johannes Schindelin
2009-08-24 16:52 ` Johannes Schindelin
2009-08-24 17:27 ` Nicolas Pitre
2009-08-24 20:10 ` Peter Harris
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=a1b6cb1b0908240442t676a13a2ma706c489e3c06860@mail.gmail.com \
--to=ulrik.sverdrup@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).