public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: "Gary Thomas" <gary@mlbassoc.com>
To: "Daly, Jeffrey" <jeffrey.daly@intel.com>
Cc: gary@mlbassoc.com, ecos-maintainers@ecos.sourceware.org
Subject: Re: contributing to eCos
Date: Thu, 15 Jan 2004 21:19:00 -0000	[thread overview]
Message-ID: <3332.208.186.29.82.1074201587.squirrel@www.chez-thomas.org> (raw)
In-Reply-To: <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
------------------------------------------------------------

       reply	other threads:[~2004-01-15 21:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BF1FE1855350A0479097B3A0D2A80EE0F60C25@hdsmsx402.hd.intel.com>
2004-01-15 21:19 ` Gary Thomas [this message]
2004-01-16  1:44   ` Jonathan Larmour

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=3332.208.186.29.82.1074201587.squirrel@www.chez-thomas.org \
    --to=gary@mlbassoc.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=jeffrey.daly@intel.com \
    /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).