User Details
- User Since
- May 17 2014, 3:06 AM (609 w, 6 d)
Yesterday
Thu, Jan 22
Tue, Jan 20
Mon, Jan 19
Fri, Jan 16
Wed, Jan 14
Sun, Jan 11
Fri, Jan 9
Thu, Jan 8
Wed, Jan 7
can you also fix the padding in tcp-state?
Tue, Jan 6
Your use of “Obtained from” is incorrect, unless “Hewlett Packard Enterprise” is the name of a piece of open-source software I've never heard of that has a copy of our libutil and already had this patch. You probably want to use “Sponsored by” instead.
Sat, Jan 3
There is no reason not to allow EDDSA. It just did not yet exist when this script was written.
Fri, Jan 2
Wed, Dec 31
I've verified that graphics/drm-66-kmod builds cleanly with these changes.
The summary is incorrect. Early operating systems including DEC's TOPS-10 and VMS used CR LF because that was what teletypes expected. CP/M was heavily inspired by TOPS-10 and continued to use CR LF despite rarely if ever being used with teletypes. DOS inherited CR LF from CP/M, and Windows inherited it from DOS; Windows NT and OS/2 borrowed heavily from VMS which also used CR LF, in addition to needing to remain compatible with DOS and pre-NT Windows. Apple historically used CR but switched to LF with Mac OS X (later renamed to macOS). Unix and its descendants (such as Plan 9) have always used LF despite originally being written for teletypes, relying instead on the device driver to inject a CR if needed.
What's the point of copying the NetBSD tests if we end up having to change everything about them, and then end up adding our own test script anyway as you do in D54265?
Mon, Dec 29
I did indeed write sockstat(8) but I did not write (most of) formataddr(), and I certainly would not have approved it if asked to review it.
