From: don bailey <don.bailey@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] probably problematic primes
Date: Wed, 9 May 2007 17:22:48 -0600 [thread overview]
Message-ID: <464257C8.5030002@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Oops, didn't register the 2^n instead of 2^(n-1). Nevermind.
Don
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGQlemyWX0NBMJYAcRAoeXAJ4jgwz2etD7Cdbb5MUbzCEezo/YugCdEHkc
8kkyHoTH29qjvD0BCBcFepI=
=k7L2
-----END PGP SIGNATURE-----
next reply other threads:[~2007-05-09 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 23:22 don bailey [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-09 23:16 don bailey
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=464257C8.5030002@gmail.com \
--to=don.bailey@gmail.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).