From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id F0C58A0C46; Fri, 17 Sep 2021 15:36:16 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 74315406B4; Fri, 17 Sep 2021 15:36:16 +0200 (CEST) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by mails.dpdk.org (Postfix) with ESMTP id D653B40689 for ; Fri, 17 Sep 2021 15:36:14 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10109"; a="283806076" X-IronPort-AV: E=Sophos;i="5.85,301,1624345200"; d="scan'208";a="283806076" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Sep 2021 06:36:13 -0700 X-IronPort-AV: E=Sophos;i="5.85,301,1624345200"; d="scan'208";a="472279477" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.31.47]) by fmsmga007-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 17 Sep 2021 06:36:12 -0700 Date: Fri, 17 Sep 2021 14:36:08 +0100 From: Bruce Richardson To: dev@dpdk.org Message-ID: References: <20201022145944.470054-1-bruce.richardson@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dpdk-dev] [RFC PATCH 0/3] add custom logging to DPDK meson runs X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, Sep 15, 2021 at 05:23:24PM +0100, Bruce Richardson wrote: > On Thu, Oct 22, 2020 at 03:59:41PM +0100, Bruce Richardson wrote: > > While the meson.log file in each build directory contains lots of > > information, much of it is not of interest to developers, and it can be > > hard to see the explicitly messages from the dpdk build files among all > > the rest of the content. Futhermore, while at the end of the a > > configuration run we print out the list of enable/disabled components, > > this is never recorded anywhere for anyone who wants to check that build > > configuration later. > > > > This patchset attempts to solve these issues by supporting a > > dpdk-meson.log file in each DPDK build folder containing the output from > > the DPDK meson.build files - including the final summary information for > > later checking. > > > > Bruce Richardson (3): > > build: add a dpdk-specific meson log file > > build: shorten top-level build file > > build: write messages to dpdk build log file > > > Ping on this old RFC set. > > From lack of interest, I'd suggest we drop this set from patchwork as > "Rejected", but if others do thing it's worth pursuing I can investigate > doing a v2, to update to latest codebase. > No further feedback received. Marking as rejected to avoid filling up patchwork.