Hah, got you beat: https://github.com/eki3z/mise.el/pull/12/files
It's one ASCII character, so a one-byte patch. I don't think you can get smaller than that.
Hah, got you beat: https://github.com/eki3z/mise.el/pull/12/files
It's one ASCII character, so a one-byte patch. I don't think you can get smaller than that.
You might say, "nay! the octal triple of a file's unix permissions requires 3+3+3 bits, which is 9, which is greater than the 8 bits of a single ascii character!"
But, actually, Git does not support any file permissions other than 644 and 755. So a change from one to the other could theoretically be represented in just one bit of information.
I wonder if file deletion is theoretically even smaller than permission change.
No one counts the path being changed, just like they also don't count the commit message, committer and author name/email, etc.
Git also supports mode 120000 (symbolic links), so you could add another bit of information there.
It does not but kinda does, git stores the entire unix mode in the tree object (in ascii encoded octal to boot), it has a legacy 775 mode (which gets signaled by fsck —strict, maybe, if that’s been fixed), and it will internally canonicalise all sorts of absolute nonsense.
It took the group several years to narrow in on.
https://dolphin-emu.org/blog/2014/01/06/old-problem-meets-it...
This comment has been delayed by about 12 hours due to the Hacker News rate limit.
I did find it a little funny that my patch was so small but my commit message was so long. Also, I haven't successfully landed it yet, I keep being too lazy to roll more versions.
I feel like a bit of a fraud because this was the PR that got me the "Mars 2020 Contributor" badge...