From: "David A. Wheeler" <dwheeler@dwheeler.com>
To: Paul Jackson <pj@sgi.com>
Cc: git@vger.kernel.org
Subject: Re: Yet another base64 patch
Date: Sun, 17 Apr 2005 02:38:10 -0400 [thread overview]
Message-ID: <42620452.4080809@dwheeler.com> (raw)
In-Reply-To: <20050416210513.1ba26967.pj@sgi.com>
Paul Jackson wrote:
> David wrote:
>
>>It's a trade-off, I know.
>
>
> So where do you recommend we make that trade-off?
I'd look at some of the more constraining, yet still
common cases, and make sure it worked reasonably
well without requiring magic. My list would be:
ext2, ext3, NFS, and Windows' NTFS (stupid short filenames,
case-insensitive/case-preserving). Samba shouldn't be
more constraining than NTFS, and I would expect ReiserFS
wouldn't be a constraining case. Bonus points if the
names lengths are inside POSIX guarantees, but I bet the
POSIX limits are so tiny as to be laughable. Bonus points for
CD-ROM format with the Rock Ridge extensions (I _think_ DVDs
and later use that format too, yes?), though if that
didn't work tar files are an easy workaround. Imagine a full
Linux kernel source repository, for 30+ (pick a number) years..
can the filesystems handle the number of objects in those cases?
If it works, your infrastructure should be sufficiently
portable to "just work" on others too.
Anyway, my two cents.
--- David A. Wheeler
next prev parent reply other threads:[~2005-04-17 6:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 4:19 Yet another base64 patch H. Peter Anvin
2005-04-14 2:24 ` Christopher Li
2005-04-14 5:36 ` H. Peter Anvin
2005-04-14 2:42 ` Christopher Li
2005-04-14 6:27 ` H. Peter Anvin
2005-04-14 6:35 ` H. Peter Anvin
2005-04-14 7:40 ` Linus Torvalds
2005-04-14 16:58 ` H. Peter Anvin
2005-04-14 17:42 ` Linus Torvalds
2005-04-14 19:11 ` bert hubert
2005-04-14 19:25 ` H. Peter Anvin
2005-04-14 21:47 ` bert hubert
2005-04-15 0:44 ` Linus Torvalds
2005-04-15 1:06 ` H. Peter Anvin
2005-04-17 4:10 ` David Lang
2005-04-18 6:23 ` H. Peter Anvin
2005-04-15 1:07 ` H. Peter Anvin
2005-04-15 3:58 ` Paul Jackson
2005-04-17 3:53 ` David A. Wheeler
2005-04-17 4:05 ` Paul Jackson
2005-04-17 6:38 ` David A. Wheeler [this message]
2005-04-17 8:16 ` Paul Jackson
2005-04-17 17:51 ` David A. Wheeler
2005-04-17 18:19 ` Petr Baudis
2005-04-18 5:13 ` David A. Wheeler
2005-04-18 12:59 ` Kevin Smith
2005-04-18 16:42 ` David A. Wheeler
2005-04-17 14:30 ` Daniel Barkalow
2005-04-17 16:29 ` David A. Wheeler
2005-04-14 4:25 ` H. Peter Anvin
2005-04-14 8:17 ` Linus Torvalds
2005-04-14 17:02 ` H. Peter Anvin
2005-04-15 23:55 ` Paul Dickson
2005-04-18 6:28 ` H. Peter Anvin
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=42620452.4080809@dwheeler.com \
--to=dwheeler@dwheeler.com \
--cc=git@vger.kernel.org \
--cc=pj@sgi.com \
/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).