From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tamas K Lengyel Subject: Re: [PATCH V6 04/13] xen: Rename mem_event to vm_event Date: Wed, 18 Feb 2015 16:55:42 +0100 Message-ID: References: <1424218303-11331-1-git-send-email-tamas.lengyel@zentific.com> <1424218303-11331-5-git-send-email-tamas.lengyel@zentific.com> <54E46D6A0200007800060F85@mail.emea.novell.com> <1424262111.5799.17.camel@terminator> <54E4A32A0200007800061161@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54E4A32A0200007800061161@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Tim Deegan , "Tian, Kevin" , "wei.liu2@citrix.com" , Ian Campbell , Steven Maresca , Stefano Stabellini , Tamas K Lengyel , Ian Jackson , "xen-devel@lists.xen.org" , "Dong, Eddie" , Andres Lagar-Cavilla , Jun Nakajima , "rshriram@cs.ubc.ca" , Keir Fraser , Daniel De Graaf , "yanghy@cn.fujitsu.com" List-Id: xen-devel@lists.xenproject.org On Wed, Feb 18, 2015 at 2:35 PM, Jan Beulich wrote: >>>> On 18.02.15 at 13:21, wrote: >> On Wed Feb 18 2015 10:46:02 AM CET, Jan Beulich wrote: >> >>> > > > On 18.02.15 at 01:11, wrote: >>> > diff --git a/xen/common/mem_event.c b/xen/common/vm_event.c >>> > similarity index 59% >>> > rename from xen/common/mem_event.c >>> > rename to xen/common/vm_event.c >>> >>> Looking at this already quite huge delta I can't really see why >>> adjusting white space at once would make it much worse. In any >>> case better than leaving white space damage behind. >> >> I did that in the first version of the patch and the feedback I got was that >> it is unreviewable that way. > > Not really - in the first version of the patch the old file gets removed > as a whole, and the new file added. Same in v2 afaics, where indeed > you got such a comment. > > Jan I would rather prefer it all being done in one patch but unfortunately git can't keep track of the code movement that way. I'm not aware of any option to git to achieve all this in one patch. Tamas