From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Horman Subject: Re: [PATCH] xenvirt: Fix build break on cmdline_parse_etheraddr call Date: Thu, 18 Dec 2014 14:57:18 -0500 Message-ID: <20141218195718.GD18008@hmsreliant.think-freely.org> References: <1418835808-18803-1-git-send-email-nhorman@tuxdriver.com> <2522675.0gKbYfjInz@xps13> <20141218112523.GA18008@hmsreliant.think-freely.org> <1720794.fdko9ZT1GJ@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev-VfR2kkLFssw@public.gmane.org To: Thomas Monjalon Return-path: Content-Disposition: inline In-Reply-To: <1720794.fdko9ZT1GJ@xps13> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Thu, Dec 18, 2014 at 01:21:31PM +0100, Thomas Monjalon wrote: > 2014-12-18 06:25, Neil Horman: > > On Wed, Dec 17, 2014 at 11:20:26PM +0100, Thomas Monjalon wrote: > > > 2014-12-17 12:03, Neil Horman: > > > > Signed-off-by: Neil Horman > > > > CC: Thomas Monjalon > > > > > > What is the meaning of CC here? > > > > > CC is a tag that git send-email understands. As it implies it cc's the post to > > the indicated email, and records that fact in the body of the commit. > > OK but why CC me when sending this patch? Typically a tree maintainer is CC'ed when submitting a patch to a list. I've done it on most, if not all of my previous patches (and where I didn't, I should have). Especially given that we're this late in the release cycle, I want to be sure you're attention is called to a build break Neil > > -- > Thomas >