[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 4/7] Rename monitor_x86.c to monitor.c and monitor_arch.h to monitor.h

  • To: Tamas K Lengyel <tamas@xxxxxxxxxxxxx>
  • From: Corneliu ZUZU <czuzu@xxxxxxxxxxxxxxx>
  • Date: Mon, 8 Feb 2016 20:55:50 +0200
  • Cc: Kevin Tian <kevin.tian@xxxxxxxxx>, Keir Fraser <keir@xxxxxxx>, Ian Campbell <ian.campbell@xxxxxxxxxx>, Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>, Jun Nakajima <jun.nakajima@xxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>
  • Comment: DomainKeys? See http://domainkeys.sourceforge.net/
  • Delivery-date: Mon, 08 Feb 2016 18:56:05 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=bitdefender.com; b=KcedlO3UusGERXLxsv2aZAiFZ6lnMkl1Sa4BIL36zwWLNPsbCGRT4hRxf2mmwNpQ8rFgBr0Abti0pGjnSThTiYIFP834RwX0RT7rN88t2wARax6keqzQfmHhyL7Gq+iMJE4y8hTv1O4llp060Txr/Tx9pyuxzd1Ihbnjh8RrpFotq5eR+ra1BYr8ptlsntCm+N3oQ0EqS7+f/Clw/qJB5Tkc+IXAIu8Qq++tv85YYvv29Z3ux1+OwaJBVg8FH+KEYCoioWYcpOK8DLoMSSGr8RGi/EGnuDLVoq/ZWpVb+2KG6Obx641pEmQV2nDsZMsYMS46LCmX5CPJLGJdmwVDOA==; h=Received:Received:Received:Received:Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:X-BitDefender-Scanner:X-BitDefender-Spam:X-BitDefender-SpamStamp:X-BitDefender-CF-Stamp;
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 2/8/2016 8:18 PM, Tamas K Lengyel wrote:

On Mon, Feb 8, 2016 at 9:57 AM, Corneliu ZUZU <czuzu@xxxxxxxxxxxxxxx> wrote:
(last commit before this one explains why this was necessary)

Signed-off-by: Corneliu ZUZU <czuzu@xxxxxxxxxxxxxxx>

I assume this patch will be gone in the next iteration after using -M so skipping it now.


No, originally I intended to use the -M option, I just forgot.
This is needed even w/ the -M option.
The reason is git seeing file <somepath1>/a.c as being modified
when moving it to <somepath2>/a.c and at the same time adding
<somepath1>/a.c in place of the old one, *even if* the similarity
between the old <somepath1>/a.c and <somepath2>/a.c would be *100%*
and you'd use the -M option. A google-search led me to a 2009-dated page
that described this as a lack of git diff's algo that would be improved upon.
It seems they aren't there yet.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.