On Wed, Feb 18, 2015 at 2:35 PM, Jan Beulich <jbeul...@suse.com> wrote: >>>> On 18.02.15 at 13:21, <tamas.k.leng...@gmail.com> wrote: >> On Wed Feb 18 2015 10:46:02 AM CET, Jan Beulich <jbeul...@suse.com> wrote: >> >>> > > > On 18.02.15 at 01:11, <tamas.leng...@zentific.com> 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
