From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: [PATCH 1/6] librte_log: add function to retrieve log_level Date: Fri, 13 Nov 2015 14:04:02 -0500 Message-ID: <20151113190402.GD25051@mhcomputing.net> References: <1447397258-27233-1-git-send-email-mhall@mhcomputing.net> <1447397258-27233-2-git-send-email-mhall@mhcomputing.net> <20151113114008.GA15612@bricha3-MOBL3> <4536748.1MnZAysZE1@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id E7E7E9573 for ; Fri, 13 Nov 2015 20:04:02 +0100 (CET) Content-Disposition: inline In-Reply-To: <4536748.1MnZAysZE1@xps13> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, Nov 13, 2015 at 12:49:36PM +0100, Thomas Monjalon wrote: > I'm sad for you Bruce: you only see an empty line where you could catch > the beauty of the star ;) +1 > Matthew, obviously you failed your send. You might find a more polite way than calling contributions failures. ;) > As a general comment, please group patches by logic meaning and > check them before sending ;) I did. But I'm a community guy and this is not full-time employment, and I am admittedly quite bad at git email workflow and don't like it much as discussed in previous threads. So I did the best I could do but screwed up something minor at approx 1 or 2 AM. It happens. I don't send you guys crazy emails when there is a build failure upstream either you know. (: Matthew.