-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for using Chaosnet streams (provided by cbridge). #22
Conversation
Don't translate it, just show it. See RFC 734, bottom of page 3.
Send input and output speeds, and the local userid (first 6 chars). Plus don't crash when debug is turned on.
Clear the line for "Connection closed" and also after, to make the message more readable.
of the Chaosnet stuff.
...of the Chaos stuff. But really, the rest should also be cleaned up.
Sorry, I'll redo with another fix. |
FYI, you can push new commits and force-push to update a pull request
any time you like.
|
I guessed there must be a way. I'll try that next time! :-) |
So how, more precisely, would I update the latest pull request into PDP-10:master with the latest commits in Chaosnet:master? |
I think you already did it. By pushing new commits to Chaosnet:master, they were automatically added here: When you make a pull request, GitHub will monitor the repository and branch originally used to open the request. The pull request will always reflect the state of that branch. You can also completely rewrite the history on that branch and force push it, and the pull request will be updated accordingly. |
If the host parameter given can be on Chaosnet (based on DNS or that it's a valid 16-bit chaos address), connect using the stream interface of cbridge, else use Internet as usual.
Also send three extra Supdup variables (supported by ITS), and some minor things.