github-docs VS wine-tkg-git

In college, an English professor would ask me and other students the following question when reviewing our essays, “Where are the examples?” Developers ask the same question when reading your documentation. To write good technical writing documents, include examples that developers can see themselves implementing in their work. How can this be done? By adding examples from your product’s codebase! 🙂 Let’s look at this code snippet from my contribution to GitHub’s documentation:

Need an example? Check the GitHub docs contributing guide.

git clone https://github.com/github/docs.git 123.57s user 37.02s system 74% cpu 3:35.73 total

git clone --depth 1 https://github.com/github/docs.git 3.37s user 1.83s system 35% cpu 14.521 total

Not a scientific test at all, but the second one was literally 35x faster, wall clock time.

Docs

The strange thing is that I only have this problem with github, all other websites work just fine. And even docs.github.com works fine...

99.9 at best for enterprise cloud: https://github.com/github/docs/blob/main/content/site-policy/site-policy-deprecated/github-enterprise-service-level-agreement.md

A project repository typically has a license file at the top-level indicating which license the code falls under. See here for an example license file.

NTSync still seems to outperform any userspace fsync implementation https://github.com/Frogging-Family/wine-tkg-git/issues/936#i...

See: https://github.com/Frogging-Family/wine-tkg-git/issues/936

The exact version that I'm using: https://github.com/Frogging-Family/wine-tkg-git/actions/runs/4806748824

Clone the wine tkg git repo: git clone https://github.com/Frogging-Family/wine-tkg-git

Can't use native bcrypt.dll however Valve's proton uses a patched version. Wine-tkg uses Valve's version, might want to give it a try.