3 ms·
This is awesome. Especially the fact that it's built-in and easy to turn on. Seams like quite a complex solution though. I guess some big company (Microsoft?)
by mpawelski 4y ago
This is awesome. Especially the fact that it's built-in and easy to turn on.
Seams like quite a complex solution though. I guess some big company (Microsoft?) implemented it internally for their own use and later tried to move it to upstream git. I wonder if there was some pushback from git maintainers from having this functionality built-in.
Also why for Windows they use named pipes when in theory Windows also supports it? (https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/ https://devblogs.microsoft.com/commandline/af_unix-comes-to-...)
BTW, to the author of this article. It is very good. It was an interesting read. The are some small issues:
- "markdown" link didn't get converted to html: "[core.untrackedcache](https://git-scm.com/docs/git-config#Documentation/git-config.txt-coreuntrackedCache https://git-scm.com/docs/git-config#Documentation/git-config...)"
- the link to "philosophy" of Scalar doesn't work: https://github.com/microsoft/git/blob/HEAD/contrib/scalar/docs/philosophy.md https://github.com/microsoft/git/blob/HEAD/contrib/scalar/do...
- mappu 4y agoGit for Windows currently supports Vista and above - the AF_UNIX support was only added in Windows 10 1803. Named pipes are fine, the semantics are basically identical, and you can guarantee there is a separate namespace versus the filesystem (for AF_UNIX, \x00 prefixes work on Linux but not on macOS).