From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-trace-devel-owner@vger.kernel.org Received: from mail-wm0-f65.google.com ([74.125.82.65]:44046 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752847AbdLRPfH (ORCPT ); Mon, 18 Dec 2017 10:35:07 -0500 Received: by mail-wm0-f65.google.com with SMTP id t8so29869525wmc.3 for ; Mon, 18 Dec 2017 07:35:06 -0800 (PST) Message-ID: <1513611304.2904.7.camel@gmail.com> Subject: Re: [RFC PATCH v3 0/9] trace-cmd: restructure of the source tree [incomplete] From: Vladislav Valtchev To: Steven Rostedt Cc: y.karadz@gmail.com, linux-trace-devel@vger.kernel.org Date: Mon, 18 Dec 2017 17:35:04 +0200 In-Reply-To: <20171213105318.5d8b3056@gandalf.local.home> References: <20171212162534.31144-1-vladislav.valtchev@gmail.com> <20171212193004.05efce2e@gandalf.local.home> <1513173368.2565.64.camel@gmail.com> <20171213105318.5d8b3056@gandalf.local.home> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-trace-devel-owner@vger.kernel.org List-ID: On Wed, 2017-12-13 at 10:53 -0500, Steven Rostedt wrote: > Do it in the next non-RFC patch set. I think you are starting to get > the idea of what I want. And there's no reason to have it RFC. The next > series may still not be ready to go in, but that's why we have v2, v3, > v4... notations ;-) > Sure, no problem. I'm working on it.