linux-kernel - Re: [GIT PULL] x86: use arch/x86/include

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4890B153.6050305@zytor.com>
Date:	Wed, 30 Jul 2008 11:22:11 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Sam Ravnborg <sam@...nborg.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Jeff Dike <jdike@...toit.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [GIT PULL] x86: use arch/x86/include

Ingo Molnar wrote:
> * Sam Ravnborg <sam@...nborg.org> wrote:
> 
>> Hi x86 guys.
>>
>> It turned out to be easy to enable um to use arch/x86/include so here 
>> is a git pull.
> 
> hm, we have a _ton_ of changes to include files queued up already, so 
> this is rather inconvenient.

Git *should* be able to track those changes across a rename and even 
with a rename on one branch and changes on another; in my experience it 
works well for filename renames, but git doesn't understand directory 
renames at all, so new files do have to be moved to their new locations 
manually.

> I missed the discussion on this, what's the point of renaming all these 
> files?

I know there has been talk about this on and off for a long time (to get 
all the arch code into arch/).  I don't know if there are any mechanical 
reasons for it, on top of that.

	-hpa

--
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/