Eric Swenson

Notice, the first time, it appeared that TECO hung. We never got the output line confirming the compression of EMACS1; CCL >. And thus, never finished PURIFY, and thus never...

Well, it appears to be the timestamps. The three errors I get under macOS are: ```touch -h -t "198904020211.39" -- "emacs1/vt52.4" touch: invalid date format ‘198904020211.39’ touch -h -t "198904020211.45"...

Very weird: ``` ➜ its git:(master) ✗ touch -h -t 198904020104.03 src/emacs1/vt52.4 ➜ its git:(master) ✗ touch -h -t 198904020204.03 src/emacs1/vt52.4 touch: invalid date format ‘198904020204.03’ ➜ its git:(master) ✗...

I see things differently than Chris. For me, the "bad" timestamp doesn't work on any files, existing or non-existing: ``` ➜ its git:(master) ✗ touch ~/tmp/foo ➜ its git:(master) ✗...

Once LIBDOC; RDTAGS > is updated to not reference the AI machine to load KEN; DECLAR >, then KEN; DECLAR > must be updated to not reference AI: KEN; DECLA2....

Couldn't find the source for KEN; GCDEMN FASL, so I decided to try to use the one in LIBLSP. However, I could not compile LIBLSP; #PRINT RCW3. First, this uses...

What mechanism do we have on ITS now to print? I think it would be great to have an emulated XGP so that we can print arbitrary files, TeX output,...

Doesn't midas include the assembly date/time in the binary? Or is .;@ TECO not an SBLK file?

I think we should include the sources in our source tree, despite not building or using them. Otherwise they might become lost again.

Yes, being in the repository is good. But it might be nice, for those who are building and installing their own ITS systems to actually have them in the loaded...