From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Peres Subject: Re: [Mesa-dev] rules for merging patches to libdrm Date: Tue, 19 Nov 2013 16:14:38 +0100 Message-ID: <528B805E.8080800@free.fr> References: <528B7E01.4080101@vodafone.de> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; Format="flowed" Content-Transfer-Encoding: quoted-printable Return-path: Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) by gabe.freedesktop.org (Postfix) with ESMTP id 1BDEAFB485 for ; Tue, 19 Nov 2013 07:14:45 -0800 (PST) Received: from [147.210.128.191] (unknown [147.210.128.191]) (Authenticated sender: martin.peres) by smtp4-g21.free.fr (Postfix) with ESMTPA id 0DE8E4C81CC for ; Tue, 19 Nov 2013 16:14:39 +0100 (CET) In-Reply-To: <528B7E01.4080101@vodafone.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org Le 19/11/2013 16:04, Christian K=F6nig a =E9crit : > So I think the very first step should be to publish everything on the = > appropriate lists, and not try an approach like releasing the kernel = > code first and waiting for it to show up upstream and then try to = > release the userspace code build on top of it. Sure, that's why we have private repos and mailing lists. Steps would be: - Make a mergeable working prototype you are satisfied with - Publish all the parts as private repos - Request for comments and go to step 0 until everyone is satisfied - Merge it in the kernel, then libdrm, then ddx and mesa This is pretty much what everyone does already, so I agree with Jerome = here, No need for a maintainer here as long as people remember that. = Thanks Dave for spotting this bad behaviour and reminding us of the rule. Martin