From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [80.91.229.2] (helo=ciao.gmane.org) by linuxtogo.org with esmtp (Exim 4.68) (envelope-from ) id 1JP5gM-0005rd-M2 for openembedded-devel@openembedded.org; Wed, 13 Feb 2008 01:41:02 +0100 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JP5ga-0003L2-6X for openembedded-devel@openembedded.org; Wed, 13 Feb 2008 00:41:16 +0000 Received: from ip-62-143-227-114.1411n-cud12k-01.ish.de ([62.143.227.114]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 13 Feb 2008 00:41:16 +0000 Received: from no2spam by ip-62-143-227-114.1411n-cud12k-01.ish.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 13 Feb 2008 00:41:16 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: openembedded-devel@openembedded.org From: Rolf Leggewie Date: Wed, 13 Feb 2008 01:41:02 +0100 Message-ID: Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip-62-143-227-114.1411n-cud12k-01.ish.de User-Agent: Thunderbird 2.0.0.6 (X11/20071022) Sender: news Subject: [RFC] push those patches, push'em up X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2008 00:41:02 -0000 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Hi, OE has quite many patches that are just too valuable to keep to ourselves. In the spirit of our bug sprint weekends, I want to propose patch-pushing weekends. Maybe we can even replace the former with the latter. I'd like to propose the coming weekend as the first of this kind. To get everybody on the same page and to make sure this is a sustainable effort, I'd also like to propose some soft policy for patches committed to OE. This should help us quickly find those patches still in need of some pushing. 1) first line in a patch starts with upstream: and goes on to list the URL where the bug has been reported upstream. 2) further information can optionally be listed in the following fields * status: pending, accepted in XXX, rejected * origin: where the patch has been stolen ;-) * comment: any further detail such as description or reason for application of the patch Comments? Volunteers to join the cause? Regards Rolf