From: Tad Hunt tad@elwood-low.csh.rit.edu
Subject: DEC pmax support in vl (W/O broken attachments)
Date: Sun, 3 Nov 1996 13:37:34 -0500 [thread overview]
Message-ID: <19961103183734.EoCRO0jVZYwaV1aKUTFp6A30MysJGpm1Wn04NVCi_qI@z> (raw)
In message <199611031831.NAA25084@mcp.csh.rit.edu>, you said:
;------- =_aaaaaaaaaa0
;Content-Type: text/plain; charset="us-ascii"
;Content-ID: <21904.847045875.1@elwood-low.csh.rit.edu>
;
; Looks like I screwed up the attachments. This is attempt number 2.
;
;
; I'm working on porting plan9 to the DEC pmax. The pmax is a little
; endian based mips port. Step one was to make the plan9 mips toolset outpu
;t
; little endian code. The following 3 diffs patch vl(1) to make bootable
; pmax code.
;
; -Tad
Ok, the attachments are still a bit broken. I thought the '.'s in the first
column were screwing my mailer up, so I doubled them... guess what, that
doesn't seem to have been the problem. So just do this little sed(1)ism on
the diffs: 's/^\.\.$/\./'
-Tad
next reply other threads:[~1996-11-03 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-03 18:37 Tad [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-11-03 18:31 Tad
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19961103183734.EoCRO0jVZYwaV1aKUTFp6A30MysJGpm1Wn04NVCi_qI@z \
--to=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).