From: Paul Nasrat <pauln@truemesh.com>
To: Robert de Bath <robert$@mayday.cix.co.uk>
Cc: Riley Williams <rhw@InfraDead.Org>,
Manuel Novoa III <mjn3@codepoet.org>,
Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: More dev86 changes (0.16.5)
Date: Wed, 24 Jul 2002 23:26:32 +0100 [thread overview]
Message-ID: <20020724222631.GA7170@raq465.uk2net.com> (raw)
In-Reply-To: <449ac7bad6f7380a@mayday.cix.co.uk>
On Wed, Jul 24, 2002 at 10:17:16PM +0100, Robert de Bath wrote:
>
> > 1) #elif support.
> In 0.16.5
<snip>
Hi Rob,
To take Gregg's post to a tangent.
I'd quite like to at least attempt to contribute to linux-86/elks libc.
I've played with ucLibc and also dredged up some stuff in the cvs
repostiory merged from dev86 but not in dev86 releases, and that confuses
me...
It's moved since my last attempt to try and get involved (and failing
due to slackness)
http://cvs.uclinux.org/cgi-bin/cvsweb/uClibc/libc/inet/addr.c?rev=1.1&content-type=text/x-cvsweb-markup
I'd quite like to see dev86 with a cvs repository so I can look over
different versions to learn about things. I'd understand if you don't
want to bother merging past stuff into a repostiory but just out of
curiosity in terms of compiler stuff, libc stuff, and asm I'd like to
be able to easily see the stuff you're doing.
I may not be good enough to contribute, but if you can at least cvs it,
and give access to that, it'd be an education.
Cheers
Paul
next prev parent reply other threads:[~2002-07-24 22:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 14:05 C compiler, assembler and linker Harry Kalogirou
2002-07-14 17:27 ` Manuel Novoa III
2002-07-15 6:07 ` Riley Williams
2002-07-15 17:02 ` Manuel Novoa III
2002-07-15 19:13 ` Riley Williams
2002-07-15 22:02 ` Manuel Novoa III
2002-07-16 6:27 ` Riley Williams
2002-07-17 1:31 ` Manuel Novoa III
2002-07-17 6:33 ` Riley Williams
2002-07-18 12:03 ` Minix vs. ELKS Feher Tamas
2002-07-18 12:27 ` Javier Sedano
2002-07-02 15:07 ` (unknown) Miguel A. Bolanos
2002-07-18 13:40 ` Minix vs. ELKS Alan Cox
2002-07-22 21:41 ` C compiler, assembler and linker Robert de Bath
2002-07-23 8:16 ` Robert de Bath
2002-07-23 16:25 ` Manuel Novoa III
2002-07-23 19:09 ` Robert de Bath
2002-07-24 21:17 ` More dev86 changes (0.16.5) Robert de Bath
2002-07-24 22:02 ` Riley Williams
2002-07-25 15:42 ` Manuel Novoa III
2002-07-26 7:55 ` Robert de Bath
2002-07-26 15:12 ` Manuel Novoa III
2002-07-26 8:22 ` Robert de Bath
2002-07-24 22:26 ` Paul Nasrat [this message]
2002-07-25 16:34 ` Manuel Novoa III
2002-07-22 23:26 ` C compiler, assembler and linker Robert de Bath
2002-07-23 0:34 ` Riley Williams
2002-07-23 0:58 ` Manuel Novoa III
2002-07-23 0:46 ` Manuel Novoa III
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=20020724222631.GA7170@raq465.uk2net.com \
--to=pauln@truemesh.com \
--cc=linux-8086@vger.kernel.org \
--cc=mjn3@codepoet.org \
--cc=rhw@InfraDead.Org \
--cc=robert$@mayday.cix.co.uk \
/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