3 ms·
For context, this header file was introduced during the period of Microsoft's acquisition of GitHub. Git's banned.h roughly approximates the banned functions a
by b55c63a4 7y ago
For context, this header file was introduced during the period of Microsoft's acquisition of GitHub.
Git's banned.h roughly approximates the banned functions according to Microsoft's Security Development Lifecycle: https://docs.microsoft.com/en-us/previous-versions/bb288454(v=msdn.10) https://docs.microsoft.com/en-us/previous-versions/bb288454(...
It seems Microsoft once published their own banned.h, but this file is not readily available from the MSDN anymore.
- brianpgordon 7y agoWhat are you saying is the connection between GitHub's acquisition and this header? This code is from git, not GitHub.
- OJFord 7y agoI'm also confused reading that comment, but I suppose the intended link is that GitHub employees are significant git contributors?
- philwelch 7y agoYes, I've seen other instances of Microsoft/GitHub making substantial Git contributions: https://devblogs.microsoft.com/devops/supercharging-the-git-commit-graph-iii-generations/ https://devblogs.microsoft.com/devops/supercharging-the-git-... Microsoft seemed to have been adopting Git already, so it may be that acquiring Github was merely part of a broader Git strategy that Microsoft has adopted.