linux-kernel - Re: [RFC/PATCH 06/59] mv kernel/acpi/processor.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 13 Mar 2007 14:32:07 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Steven Rostedt <rostedt@...dmis.org>
cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Chris Wright <chrisw@...s-sol.org>,
	Rusty Russell <rusty@...tcorp.com.au>, Andi Kleen <ak@....de>,
	Glauber de Oliveira Costa <glommer@...il.com>,
	Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: [RFC/PATCH 06/59] mv kernel/acpi/processor.c

On Tue, 13 Mar 2007, Steven Rostedt wrote:
>
> Move kernel/acpi/processor.c to the common hold.

Please use

	git diff -M

for things like this.

In fact, even if you weren't a git user, I'd ask you to *become* one just 
because I think that it's a *lot* more productive if people actually see 
renames as renames, and will see what - if anything - changed when 
renaming.

The "-M" flag isn't the default, simply because it generates patches that 
cannot be applied with regular "patch", but for something like this, I 
think it's practically imperative. The old kind of "remove file" + "add 
file" patch just isn't acceptable when there are very viable alternaties.

You don't even have to use a git repository to use a git rename patch - 
you just need to use "git apply" to apply it.

		Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/