DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=cqa+H0DtFN1vwsHBu59/Kki435O1T/kJnk8vO+RCREQ8mCJZn8RVC5vAAlaQ/JW2sOdCyYROaY7dSUnhc96c0eKm/Mecos7NNrijYgUbNqM3VpT+nJW/bcekkKJvRLsL25IOwrfnLkKUvWIVFgyXRHYq5JJZzYtrb/E89adSQ14=
Message-ID: <fc339e4a0502050042408c05ce@mail.gmail.com>
Date: Sat, 5 Feb 2005 17:42:58 +0900
From: Miles Bader <snogglethorpe@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [Gnu-arch-users] Re: arch performance with large trees
In-Reply-To: <tnxoeezo1he.fsf@arm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <Pine.GSO.4.58.0412211013550.13159@kekkonen.cs.hut.fi>
	<tnxu0qfd42s.fsf@arm.com> <f96d234e041221081921c6f291@mail.gmail.com>
	<1103646999.28012.117.camel@pc1117>
	<buovf98riri.fsf@mctpc71.ucom.lsi.nec.co.jp> <tnxd5vgple1.fsf@arm.com>
	<20050204131006.GB4299@linux-sh.org> <tnxu0osny96.fsf@arm.com>
	<fc339e4a0502040809164cc8b6@mail.gmail.com> <tnxoeezo1he.fsf@arm.com>
Cc: gnu-arch-users@gnu.org, Paul Mundt <lethal@linux-sh.org>,
        Cliff Brake <cliff.brake@gmail.com>, Miika Komu <miika@iki.fi>,
        miles@gnu.org
Precedence: list
Reply-To: snogglethorpe@gmail.com, miles@gnu.org
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Status: RO
Content-Length: 1744
Lines: 43
On Sat, 05 Feb 2005 08:27:41 +0000, Catalin Marinas
<catalin.marinas@arm.com> wrote:
> > BK does come with a tool to make it easy to detect renamed files in
> > patches and change them into proper renames, and Linus does use  at
> > least some of the time -- I've submitted a normal patch containing a
> > renamed file represented as big delete + a big add, and iin the
> > resulting BK changeset, it showed up as a real rename.
> 
> I tried to look at the changesets since 2.6.9 and only a few renames
> were actually shown as renames by linux.bkbits.net. The rest showed up
> as big deletes + big adds. It is also possible that the rename is
> actually shown by the bk tool but not on bkbits.net.

I think this tool generates "real" renames, and seem to show up on
bkbits.net -- e.g., if you look at the diffs for a changeset, you'll
see a file patch where the before and after names are different.

For instance, here's the bkbits diff for a patch I sent to Linus as a
normal diff (big delete + big add):

http://linux.bkbits.net:8080/linux-2.5/user=miles/diffs/drivers/serial/v850e_uart.c@1.13?nav=!-|index.html|stats|!+|index.html|ChangeSet@-2y|cset@1.1046.538.30

Notice the filenames in the diff header:

--- 1.12/drivers/serial/nb85e_uart.c	2005-02-05 00:37:24 -08:00
+++ 1.13/drivers/serial/v850e_uart.c	2005-02-05 00:37:24 -08:00

[If this is not happening for some patches, it may that Linus is
simply more lazy/busy/whatever these days and doesn't bother to use
the tool.]

-Miles
-- 
Do not taunt Happy Fun Ball.


_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/