From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Réf. : [9fans] october 14 package patch
Date: Wed, 29 Nov 2000 13:58:20 -0500 [thread overview]
Message-ID: <20001129185831.D970619A04@mail.cse.psu.edu> (raw)
exactly what i smashed into my Makefile when i wrote md5:
http://www.planete.net/~boyd/code/md5.bundle
use the whole checksum. all those bits are there for a _reason_.
I do use the whole checksum in wrap (I just don't
believe in putting the whole things on web
pages for poor humans to stare at). The problem
was that I moved some code around in wrap/create and
in one case the sum wasn't getting computed at all,
so you got whatever was on the stack, hence the
regularity. The MD5 code was from a library that
has been correct for a good long time.
Russ
next reply other threads:[~2000-11-29 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 18:58 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-29 13:27 boyd.roberts
2000-11-29 11:17 boyd.roberts
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=20001129185831.D970619A04@mail.cse.psu.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).