git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Yet another base64 patch

From
David A. Wheeler <dwheeler@dwheeler.com>
Date
Apr 17, 2005, 03:53 UTC
Message-ID
<4261DDBC.3050706@dwheeler.com>
In-Reply-To
<20050414205831.01039ee8.pj@engr.sgi.com>
Paul Jackson wrote:
Show 11 quoted lines
> Earlier, hpa wrote:
> 
>>The base64 version has 2^12 subdirectories instead of 2^8 (I just used 2 
>>characters as the hash key just like the hex version.)
> 
> Later, hpa wrote:
> 
>>Ultimately the question is: do we care about old (broken) filesystems?
> 
> 
> I'd imagine we care a little - just not alot.

Some people (e.g., me) would really like for "git" to be more forgiving of nasty filesystems, so that git can be used very widely. I.E., be forgiving about case insensitivity, poor performance or problems with a large # of files in a directory, etc. You're already working to make sure git handles filenames with spaces & i18n filenames, a common failing of many other SCM systems.

If "git" is used for Linux kernel development & nothing else, it's still a success. But it'd be even better from my point of view if "git" was a useful tool for MANY other projects. I think there are advantages, even if you only plan to use git for the kernel, to making "git" easier to use for other projects. By making git less sensitive to the filesystem, you'll attract more (non-kernel-dev) users, some of whom will become new git developers who add cool new functionality.

As noted in my SCM survey (http://www.dwheeler.com/essays/scm.html), I think SCM Windows support is really important to a lot of OSS projects. Many OSS projects, even if they start Unix/Linux only, spin off a Windows port, and it's painful if their SCM can't run on Windows then. Problems running on NFS filesystems have caused problems with GNU Arch users (there are workarounds, but now you need to learn about workarounds instead of things "just working"). If nothing else, look at the history of other SCM projects: all too many have undergone radical and painful surgeries so that they can be more portable to various filesystems.

It's a trade-off, I know.
--- David A. Wheeler
Previous: Paul JacksonNext: Paul Jackson
Message 19 of 34 in “Yet another base64 patch”
  1. H. Peter AnvinApr 14, 2005
  2. Christopher LiApr 14, 2005
  3. H. Peter AnvinApr 14, 2005
  4. Christopher LiApr 14, 2005
  5. H. Peter AnvinApr 14, 2005
  6. H. Peter AnvinApr 14, 2005
  7. Linus TorvaldsApr 14, 2005
  8. H. Peter AnvinApr 14, 2005
  9. Linus TorvaldsApr 14, 2005
  10. bert hubertApr 14, 2005
  11. H. Peter AnvinApr 14, 2005
  12. bert hubertApr 14, 2005
  13. Linus TorvaldsApr 15, 2005
  14. H. Peter AnvinApr 15, 2005
  15. David LangApr 17, 2005
  16. H. Peter AnvinApr 18, 2005
  17. H. Peter AnvinApr 15, 2005
  18. Paul JacksonApr 15, 2005
  19. David A. WheelerApr 17, 2005
  20. Paul JacksonApr 17, 2005
  21. David A. WheelerApr 17, 2005
  22. Paul JacksonApr 17, 2005
  23. David A. WheelerApr 17, 2005
  24. Petr BaudisApr 17, 2005
  25. David A. WheelerApr 18, 2005
  26. Kevin SmithApr 18, 2005
  27. David A. WheelerApr 18, 2005
  28. Daniel BarkalowApr 17, 2005
  29. David A. WheelerApr 17, 2005
  30. H. Peter AnvinApr 14, 2005
  31. Linus TorvaldsApr 14, 2005
  32. H. Peter AnvinApr 14, 2005
  33. Paul DicksonApr 15, 2005
  34. H. Peter AnvinApr 18, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.