This is the mail archive of the
ecos-maintainers@sources.redhat.com
mailing list for the eCos project.
Re: contributing to eCos
- From: "Gary Thomas" <gary at mlbassoc dot com>
- To: "Daly, Jeffrey" <jeffrey dot daly at intel dot com>
- Cc: gary at mlbassoc dot com, ecos-maintainers at ecos dot sourceware dot org
- Date: Thu, 15 Jan 2004 14:19:47 -0700 (MST)
- Subject: Re: contributing to eCos
- References: <BF1FE1855350A0479097B3A0D2A80EE0F60C25@hdsmsx402.hd.intel.com>
Daly, Jeffrey said:
> hi gary, now that i've made the current CVS version of eCos build redboot for my IXP2800 platform,
> i'm wondering how to submit patches to the mailing list? are the patches expected to be created
> using 'cvs rdiff' ? (i haven't used CVS for a while)
Since you'll be adding files to the repository, the best way
is to generate a "normal" diff. Check out the CVS tree into
a new directory. Then generate the diffs like this:
% diff -uNr <orig-CVS> <your-modififed-CVS>
Then send the changes, along with a description of what's up,
to ecos-patches@ecos.sourceware.org It's probably best to use
a MIME attachment, as many mailers mangle the patches beyond
usability.
Don't forget to make a ChangeLog file for every new package, as
well as ChangeLog entries for any files you needed to change within
the normal tree.
Finally, whatever you want to contribute has to have clear "title".
In particular, we'll need you (or Intel) to assign copyright over
the material to the FSF (the new steward of eCos). You'll also
need to have appropriate copyright boilerplate on all the files.
Note: this process and the boilerplate will probably change soon
as the use of FSF is still new.
I've copied the rest of the maintainers into this, in case there
are any other questions or issues that I've missed.
Thanks for contributing to eCos.
------------------------------------------------------------
Gary Thomas |
MLB Associates | Consulting for the
+1 (970) 229-1963 | Embedded world
http://www.mlbassoc.com/ |
email: <gary@mlbassoc.com> |
gpg: http://www.chez-thomas.org/gary/gpg_key.asc
------------------------------------------------------------