From: Andrew Lunn <andrew@lunn.ch>
To: Brian Austin <brian.austin@cirrus.com>
Cc: ecos-dev <ecos-devel@ecos.sourceware.org>
Subject: Re: questions about code contribution
Date: Fri, 17 Nov 2006 03:46:00 -0000 [thread overview]
Message-ID: <20061117034609.GA30937@lunn.ch> (raw)
In-Reply-To: <1163713080.13482.24.camel@localhost.localdomain>
On Thu, Nov 16, 2006 at 03:38:00PM -0600, Brian Austin wrote:
> Hello all,
>
> This is Brian Austin here at Cirrus Logic.
>
> As you know we have a series or ARM9 procs that we use redboot for.
> I am cleaning up the code, as it got very dirty over the past few years,
> and was wondering if I could, once it's clean, submit it to the
> maintainers of ecos?
Sure, we are happy to access contributions.
> Will there be a review process involved?
Yes. The maintainers will review the code.
> I have several more questions about it all, but just want to put the
> first important one out there.
There is also some paper work involved. Please take a look at:
http://ecos.sourceware.org/assign.html
Andrew
prev parent reply other threads:[~2006-11-17 3:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 3:35 Brian Austin
2006-11-17 3:46 ` Andrew Lunn [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=20061117034609.GA30937@lunn.ch \
--to=andrew@lunn.ch \
--cc=brian.austin@cirrus.com \
--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).