4 ms·
I really appreciate that they bothered to set an artificial timestamp for these git commits, roughly 30 years before Git itself existed. The thing is, the other
by jelder 1y ago
I really appreciate that they bothered to set an artificial timestamp for these git commits, roughly 30 years before Git itself existed. The thing is, the other files do, too, and the .gitignore is full of hilariously anachronistic references.
- hu3 1y agoSpeaking about .gitignore. What is this? # MightyMoose *.mm.* I could only find this: https://github.com/MonzUn/MightyMooseCore https://github.com/MonzUn/MightyMooseCore Link to the file: https://github.com/microsoft/BASIC-M6502/blob/main/.gitignore https://github.com/microsoft/BASIC-M6502/blob/main/.gitignor... Regardless, thank you Mr. Hanselman. This is great!
- fishgoesblub 1y agoLooks to be for "Continuous Tests" [0] found through git blame [1] [0] https://continuoustests.com/ https://continuoustests.com/ [1] https://github.com/github/gitignore/commit/2183a6c531d7085e2d6f26cb59cc1a25f4b21c18 https://github.com/github/gitignore/commit/2183a6c531d7085e2...
- davey48016 1y agoI think it's that. I don't think that the .gitignore file is meant to reflect anything about when this BASIC interpreter was written, it looks like it's just a MS managed .gitignore that accounts for everything that was ever popular for development in Visual Studio, even things that have been obsolete for decades. In order to handle your most legacy C#, F#, VB.NET, or Visual C++ solutions.
- kubatyszko 1y agoditto! It was really a nice touch (pun intended since touch is what I'd use to produce such timestamps)