From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mail.openembedded.org (Postfix) with ESMTP id EECD1731F9 for ; Thu, 11 Feb 2016 16:59:20 +0000 (UTC) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga102.jf.intel.com with ESMTP; 11 Feb 2016 08:59:22 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,431,1449561600"; d="scan'208";a="46326223" Received: from jlock-mobl1.gar.corp.intel.com ([10.252.26.160]) by fmsmga004.fm.intel.com with ESMTP; 11 Feb 2016 08:59:20 -0800 Message-ID: <1455209960.3456.27.camel@linux.intel.com> From: Joshua G Lock To: Martin Samuelsson , bitbake development advancement Date: Thu, 11 Feb 2016 16:59:20 +0000 In-Reply-To: <20160127122406.GA20819@lnxmartinsa2.se.axis.com> References: <20151119125639.GC19141@lnxmartinsa2.se.axis.com> <20160114135304.GA7849@lnxmartinsa2.se.axis.com> <20160127122406.GA20819@lnxmartinsa2.se.axis.com> X-Mailer: Evolution 3.18.4 (3.18.4-1.fc23) Mime-Version: 1.0 Subject: Re: [PATCH v2] user-manual-metadata: Clarify functionality of task flag 'dirs'. X-BeenThere: bitbake-devel@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussion that advance bitbake development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 16:59:22 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Hi Martin, On Wed, 2016-01-27 at 13:24 +0100, Martin Samuelsson wrote: > Signed-off-by: Martin Samuelsson > --- > I've seen no response to this. With this being my first attempt at > making a  > contribution to bitbake, I would appreciate any feedback. Is > something e.g.  > problematic with the patch? v1 of this patch was merged: http://git.openembedded.org/bitbake/commit /?id=2fbd9e4e44f6b491cccca81fd34586fcfdeea3d3 Apologies for the lack of feedback. Unfortunately bitbake and its affiliated projects (notably OE-Core) receive a high volume of patches and it's not possible to reply to every one. It's usually safe to assume that a patch which doesn't get a response is likely to be merged at some point.  Thanks for your contribution. Joshua