From: Pavel Fedin <fedin@matek.ru>
To: ecos-devel@ecos.sourceware.org
Subject: Improvements to current CVS code.
Date: Mon, 17 Apr 2006 12:44:00 -0000 [thread overview]
Message-ID: <20060417164342.7736f947@localhost.localdomain> (raw)
Hello!
I've made some improvements to the current CVS code and would like to
commit them back. Here is a list:
1. Brought up OpenBSD TCP stack, now it builds and links. Even works
accorging to tests. With bridge and STP code.
2. Many components untied from libc. printf() replaced with
diag_printf() etc. Complex functions like getaddrinfo() can be disabled
(i've added options to the configuration). Aim of this is to decrease
code size.
3. Fixed some dependencies in the configuration.
Is it possible to get an R/W access to the CVS? Or the development is
conducted by RedHat only? What should i do then?
Kind regards.
next reply other threads:[~2006-04-17 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 12:44 Pavel Fedin [this message]
2006-04-17 12:57 ` Gary Thomas
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=20060417164342.7736f947@localhost.localdomain \
--to=fedin@matek.ru \
--cc=ecos-devel@ecos.sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).