Dan PortsThis is what pull requests used to look like.
(The last sentence is particularly remarkable!)
Several people pointed out that this change request looks more like a ticket than a pull request since the code isn't attached.
Here is the code that goes with it. Explaining how it works is left as an exercise for the reader.
Whine Spectator@dan "why you should care"
@secretasianman "user story"
Barry Rowlingson@dan @secretasianman AS A lunar module pilot I WANT TO land on the moon
@geospacedman @dan additional requirements:
1) in one piece
"Musty Bits" McGeeI'd guess @arclight has seen this but in case...
😀🚲@dan seems more like a bug report/ticket, not very precise about how to make the change, 4hr estimate.
Alison Chaiken@dan All that text goes in JIRA now instead.
Andrew
Sascha@dan Should have opened an issue first to discuss the change and reach consensus on a way forward
Irina@dan How was the lunar landing on July 20, 1969 jeopardized? I thought it went through without a glitch!
F4GRX Sébastien@irina @dan No, the 1201 and 1202 errors that happened during the last phase of the landing were unexpected. It took a quick and critical analysis from experts on the ground to determine that these errors were still GO.
In fact the spurious radar input (and Aldrin's computer display selections) overloaded the computer, which rebooted several times, but was programmed so cleverly by Margaret Hamilton and her team, that it recovered from the proper checkpoint and continued to provide guidance.
One other interesting detail is that none of the flight controllers had thought too hard about which computer alarms were safe to ignore until one of the last simulations before the launch, when the simulation supervisor hit them with a program alarm, and they needlessly called for an abort. They worked out a cheat sheet of alarm codes and what to do with them afterwards, so they were quickly able to recognize that it was OK and the real landing could continue.
LP🔸Light up the night@dan This must be one of the most historic changes in computer history
@CuriousMarc has a video documenting the actual change in Apollo 12 flight software assembly listings.
Grisha 
@dan "data amplification sheet" seems like the most pretentious way to say "extra page"
Khleedril@oxapentane @dan I thought it was magic paper...
Virginicus@oxapentane @dan NASA has a reputation to uphold.
Rupert Reynolds@oxapentane @dan Gotta have 3 words, to allow a TLA :-)
Jacob@dan @nixCraft Recommend BBC’s podcast series about the crucial minutes and the program errors 🤓🤩
https://podcasts.apple.com/dk/podcast/13-minutes-presents-the-space-shuttle/id1459657136?l=da
David Schuetz ** looking for work **@dan It was also like two days later. Fast work.
Flop_Ysh@dan management of change in engineering departments of companies implementing IATF 16949 or EN 9100 still looks the same but on docx or pptx file 😁
John Regehr@dan where’d you find this?
Jez 🍞🌹
@dan Amazing! Where are these from? I would love to use them in a version control workshop I'm running
@petrichor this and many, many other documents are available at the Virtual AGC project's library page
...which is a project that built an emulator for the Apollo guidance computer that can run the original software, which is awesome!
@dan Oh cool, thanks!
Steve has ☕️ for brains@dan I bet PRs would be more actionable if you had to fill out a form like this to file one!
Inspired by these Apollo program software change docs to have some fun with the posting form on my #blog
Klaus Frank@dan
That looks more like a ticket than a PR. Or did you just omit the diff?
That looks more like a ticket than a PR. Or did you just omit the diff?
Chris Espinosa