From: "H. Peter Anvin" <hpa@zytor.com>
To: git@vger.kernel.org
Subject: Trying base32
Date: Thu, 14 Apr 2005 00:26:47 -0700 [thread overview]
Message-ID: <425E1B37.20408@zytor.com> (raw)
Out of curiosity, I cooked up a version of git which used a flat base32,
instead of base64, repository. The goal of this is, of course, to
provide for compatibility with case-deficient filesystems.
The answer is that the base32 format is measurably slower than base64,
with a cache-hot checkout time of 19.19 seconds (as compared to 15.68
for base64.) So the length of the filenames does matter.
Anyway, I have uploaded the base32 patch onto kernel.org, and I have
moved all the git patches into:
ftp://ftp.kernel.org/pub/linux/kernel/people/hpa/git/
At this point, though, I would recommend the base64-flat patch.
-hpa
reply other threads:[~2005-04-14 7:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=425E1B37.20408@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.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).