public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Pavel Fedin <fedin@matek.ru>
Cc: eCos development <ecos-devel@ecos.sourceware.org>
Subject: Re: Improvements to current CVS code.
Date: Mon, 17 Apr 2006 12:57:00 -0000	[thread overview]
Message-ID: <1145278625.17193.4.camel@hermes> (raw)
In-Reply-To: <20060417164342.7736f947@localhost.localdomain>

On Mon, 2006-04-17 at 16:43 +0400, Pavel Fedin wrote:
>  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?

The eCos maintainers are responsible; for the most part, they are
not Red Hat employees.

The best way to get these changes into CVS is to propose them
as [separate] patches.  Break them up into manageable pieces
and send them, along with descriptions of what you've done to
  ecos-patches@ecos.sourceware.org

Also, given that these seem to be fairly substantial changes,
we'll need copyright assignment before we can incorporate them.
See http://ecos.sourceware.org/assign.html for details.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

      reply	other threads:[~2006-04-17 12:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 12:44 Pavel Fedin
2006-04-17 12:57 ` Gary Thomas [this message]

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=1145278625.17193.4.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=fedin@matek.ru \
    /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).