From: Jeff Garzik <jgarzik@pobox.com>
To: Ernst Persson <ernstp@mac.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] Bmac also needs crc32
Date: Wed, 03 Sep 2003 13:41:39 -0400 [thread overview]
Message-ID: <3F5627D3.90800@pobox.com> (raw)
In-Reply-To: <3F4F322B.5030900@mac.com>
thanks, applied
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-09-03 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 10:59 [PATCH] Bmac also needs crc32 Ernst Persson
2003-09-03 17:41 ` Jeff Garzik [this message]
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=3F5627D3.90800@pobox.com \
--to=jgarzik@pobox.com \
--cc=ernstp@mac.com \
--cc=linuxppc-dev@lists.linuxppc.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).