From: macbiesz@optonline.net (macbiesz@optonline.net)
Subject: [TUHS] 32V/I portability
Date: Tue, 11 Nov 2003 16:13:09 -0500 [thread overview]
Message-ID: <2a43b02a2631.2a26312a43b0@optonline.net> (raw)
You could set up a Sourceforge project for 32/I?
Maciek
----- Original Message -----
From: Pat Villani <Pat.Villani@hp.com>
Date: Tuesday, November 11, 2003 2:41 pm
Subject: [TUHS] 32V/I portability
> Folks,
>
> After studying the source code for a while, I found a few explicit
> and
> implicit vaxisms that need to be rectified. I'd like to purge the
> source entirely of these vaxisms, but that would mean that if
> anyone
> wants to port what I do back to VAX, they'll need to do some work.
>
> Also, this mailing list is fairly low traffic, and for now my
> activities
> are very low traffic as well. Should I set up a separate mailing
> list
> for those interested in this project?
>
> Opinions?
>
> Pat
>
> --
> Outer space is no place for a person of breeding. -- Lady Violet
> Bonham
> Carter
>
>
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/tuhs
>
next reply other threads:[~2003-11-11 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 21:13 macbiesz [this message]
2003-11-12 1:39 ` Kenneth Stailey
2003-11-12 1:44 ` Gregg C Levine
-- strict thread matches above, loose matches on Subject: below --
2003-11-11 19:41 Pat Villani
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=2a43b02a2631.2a26312a43b0@optonline.net \
--to=macbiesz@optonline.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).