From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Jeff Dike <jdike@addtoit.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL] x86: use arch/x86/include
Date: Wed, 30 Jul 2008 11:22:11 -0700 [thread overview]
Message-ID: <4890B153.6050305@zytor.com> (raw)
In-Reply-To: <20080730180411.GA7896@elte.hu>
Ingo Molnar wrote:
> * Sam Ravnborg <sam@ravnborg.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
next prev parent reply other threads:[~2008-07-30 18:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 12:49 [GIT PULL] x86: use arch/x86/include Sam Ravnborg
2008-07-30 18:04 ` Ingo Molnar
2008-07-30 18:22 ` H. Peter Anvin [this message]
2008-07-30 18:32 ` Ingo Molnar
2008-07-30 18:35 ` Linus Torvalds
2008-07-30 18:47 ` Sam Ravnborg
2008-07-30 19:19 ` Ingo Molnar
2008-07-30 19:27 ` H. Peter Anvin
2008-07-30 19:39 ` Sam Ravnborg
2008-07-31 23:15 ` Tony Luck
2008-07-31 23:17 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4890B153.6050305@zytor.com \
--to=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox