From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ecos-maintainers-return-389-listarch-ecos-maintainers=sources.redhat.com@sources.redhat.com>
Received: (qmail 6913 invoked by alias); 6 May 2003 13:26:00 -0000
Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:ecos-maintainers-subscribe@sources.redhat.com>
List-Post: <mailto:ecos-maintainers@sources.redhat.com>
List-Help: <mailto:ecos-maintainers-help@sources.redhat.com>, <http://sources.redhat.com/lists.html#faqs>
Sender: ecos-maintainers-owner@sources.redhat.com
Received: (qmail 6904 invoked from network); 6 May 2003 13:25:59 -0000
Date: Tue, 06 May 2003 13:26:00 -0000
From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Gary Thomas <gary@mlbassoc.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Patch policy
Message-ID: <20030506132550.GK24032@biferten.ma.tech.ascom.ch>
References: <1052225944.30126.4370.camel@hermes>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1052225944.30126.4370.camel@hermes>
User-Agent: Mutt/1.4i
X-Filter-Version: 1.6 (rubicon)
X-SW-Source: 2003-05/txt/msg00006.txt.bz2

> In an ideal world, patches from outside our group would
> be posted to a database which could be queried by anyone.
> Maybe the easiest way to do this would be to forward the
> patch to BugZilla.

Sounds like a reasonable idea. Let bugzilla pick the default owner of
the patch depending on the component. We would probably want to add
more HAL components, one per architecture. 

The messy thing is getting the patch from ecos-patches into
bugzilla. I don't see it being done automagically. Do we have to
retrain all contributers to use bugzilla instead of the list? Does one
of us have to import the patch?

   Andrew