From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29083 invoked by alias); 16 Jan 2004 01:44:42 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 29076 invoked from network); 16 Jan 2004 01:44:41 -0000 Message-ID: <40074205.7070609@eCosCentric.com> Date: Fri, 16 Jan 2004 01:44:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.4) Gecko/20030703 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: Gary Thomas Cc: "Daly, Jeffrey" , ecos-maintainers@ecos.sourceware.org Subject: Re: contributing to eCos References: <3332.208.186.29.82.1074201587.squirrel@www.chez-thomas.org> In-Reply-To: <3332.208.186.29.82.1074201587.squirrel@www.chez-thomas.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-01/txt/msg00010.txt.bz2 Gary Thomas wrote: > 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 > > 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. An alternative and more reliable means to submit a patch is to use our bugzilla system. These pages contain full details about generating patches, assignments, what makes a good patch etc.: http://ecos.sourceware.org/patches.html That's not to say a mail to ecos-patches would be ignored, just that in bugzilla it can be tracked properly to make sure it gets checked in. > 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. Unfortunately since this is a very recent development, the arrangement with the FSF hasn't been properly set up yet - we don't know yet whether they are accepting assignments for eCos yet, and we don't yet have access to the system that lets us know if an assignment has been made. So you can follow the instructions here about assigning to eCosCentric on a temporary basis, or you can hold off temporarily until we find out from the FSF what's going on: http://ecos.sourceware.org/assign.html Thanks! Jifl -- eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts --["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine