public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 12:27:23 -0700	[thread overview]
Message-ID: <4890C09B.3000701@zytor.com> (raw)
In-Reply-To: <20080730191907.GD26389@elte.hu>

Ingo Molnar wrote:
> 
> But fortunately you've scripted all this, so i guess we can do it at any 
> stage. Could you send the script we should run?
> 

That's really the sanest way to deal with all this.  If this is already 
automated, then we can script-generate a roving (constantly rebased) 
pseudo-branch, and apply it formally before pushing it up to Linus.

Restructuring changes are hideously messy, because they're orthogonal to 
everything else that's going on.  The x86 merge itself and all that went 
along with it is a great example.

	-hpa

  reply	other threads:[~2008-07-30 19:28 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
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 [this message]
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=4890C09B.3000701@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