From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 7E496E00978; Thu, 13 Aug 2015 07:11:22 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.118 listed in list.dnswl.org] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx2.mail.bg (mx2.mail.bg [193.201.172.118]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 29167E0096A for ; Thu, 13 Aug 2015 07:11:17 -0700 (PDT) Received: from [192.168.0.62] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx2.mail.bg (Postfix) with ESMTPSA id D0FB560011F8; Thu, 13 Aug 2015 17:11:15 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1439475076; bh=tsaJedPDuevi5Sn+xlvIgF6L24JjVBHV5Ht9hjGaIH8=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=/cCpNHBrnKBXw1+QaXRaTl+9iE6+Yli+odkhNKfXplrNxS4McKkI+rFptc1VcrBCp teIzzQ/Ft0NwAs6n6zcnh75we+F/gS5Ks+kDPJGAvdNum32QBv/9sH+RYYy4D84GM+ SIR8HBJatKaIqgnSN9HSo44ptY2nbBfoSEAFbQs8= Message-ID: <55CCA583.4090107@mail.bg> Date: Thu, 13 Aug 2015 17:11:15 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 MIME-Version: 1.0 To: Paul Sherwood References: <90967689f471f5ac0cf4edca77457a8c@codethink.co.uk> <55CC8E62.7070102@mail.bg> <0071ba1f11fafdd0812214d3da8ce4b4@codethink.co.uk> In-Reply-To: <0071ba1f11fafdd0812214d3da8ce4b4@codethink.co.uk> Cc: yocto@yoctoproject.org, Takeshi Saito , Nobuhiro Iwamatsu , automotive-discussions@lists.linuxfoundation.org Subject: Re: How to submit patches upstream for repos at git.yoctoproject.org (eg meta-renesas) X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Aug 2015 14:11:22 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Paul, On 08/13/2015 04:24 PM, Paul Sherwood wrote: > Hi Nikolay! > On 2015-08-13 13:32, Nikolay Dimitrov wrote: >> On 08/13/2015 02:21 PM, Paul Sherwood wrote: >>> Hi all, >>> I am not affiliated to any Yocto Project member organisation, but am >>> assisting with integration at the Automotive Grade Linux project, which >>> is re-using some work from upstreams at git.yoctoproject.org >>> >>> Recently members of the AGL community have started contributing patches >>> for meta-renesas at our mirror [1]. We would like to offer this and >>> future work to upstream, and I am hoping to understand so that I can >>> help guide AGL's activities so that we are properly aligned. Please can >>> someone guide us on the accepted way to offer these and subsequent >>> patches? >>> >>> br >>> Paul >>> >>> [1] https://gerrit.automotivelinux.org/gerrit/#/c/4047/ >> >> Haven't seen you for a quite a while after Karlsruhe, hope you're doing >> fine. > > Small world! I am very well thank you - it's great to re-connect with > old friends here :-) > >> Regarding the upstreaming guidelines, the usual steps apply - ask >> contributors to push patches as close to the upstream project as >> possible, and just then go downstream, like this (in order of >> preference): >> >> 1. Upstream components >> 2. Yocto meta layer (which you are reusing) >> 3. AGL repos > > Understood, thank you. So in this case, for patches to meta-renesas, > should we email them to this list, or another list, or send directly to > the maintainer, or is there another mechanism established? Usually I would advice to send the patches to a Renesas-specific ML, but I couldn't find it in the OE layers index, so it would be best to ask the Renesas team. @Stephen, Takeshi, Nobuhiro: Can you please advice which is the proper ML for sending meta-renesas patches? Thanks. >> Also, it would be great if your AGL maintainers can enforce appropriate >> patch tracking by Upstream-status tag + description, as it will help >> everyone. > > Yes, I completely agree. > > br > Paul Have a nice day, Nikolay