From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15334 invoked by alias); 3 Sep 2003 12:34:40 -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 15324 invoked from network); 3 Sep 2003 12:34:39 -0000 Date: Wed, 03 Sep 2003 12:34:00 -0000 From: Andrew Lunn To: Jonathan Larmour Cc: eCos Maintainers Subject: Re: Doc on How to submit patches Message-ID: <20030903123432.GK6488@biferten.ma.tech.ascom.ch> References: <3F5522F8.3030404@eCosCentric.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F5522F8.3030404@eCosCentric.com> User-Agent: Mutt/1.4i X-Filter-Version: 1.11a (ascomax) X-SW-Source: 2003-09/txt/msg00004.txt.bz2 On Wed, Sep 03, 2003 at 12:08:40AM +0100, Jonathan Larmour wrote: > Nick and myself have been working on this: > http://ecos.sourceware.org/patches.html > > Comments? Corrections? Abuse? The component to use in Bugzilla is "Patches and Contributions". Im humming and harring as to if it would be better to use the component the major part of the patch is in. That way it automagically gets a default owner who we can point a finger at when the patch sits around for a while with nothing happening. If the owner is overloaded its his responsibility to then find another maintainer to take over the patch. It would be nice to add a state "Waiting for assignment" to bugzilla. Andrew