mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Chris Wright <chrisw@sous-sol.org>,
	Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@muc.de>,
	Glauber de Oliveira Costa <glommer@gmail.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [RFC/PATCH 06/59] mv kernel/acpi/processor.c
Date: Tue, 13 Mar 2007 20:51:37 -0400	[thread overview]
Message-ID: <1173833497.30118.8.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0703131429260.9690@woody.linux-foundation.org>

On Tue, 2007-03-13 at 14:32 -0700, Linus Torvalds wrote:
> 
> On Tue, 13 Mar 2007, Steven Rostedt wrote:
> >
> > Move kernel/acpi/processor.c to the common hold.
> 
> Please use
> 
> 	git diff -M

OK, thanks!  I'm still quite a git-nubie.

I'll update all the move patches. It may take a bit of hand work.

What I really did to do this patch series was to make all my changes in
git.  But the changes where not smooth from change set to change set. So
I did one big git-diff, and then used good old midnight commander (mc)
to parse the patches. And then pulled them into quilt to comment and
send them.


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

I wish I knew this before breaking it up.   But I'm sure I can do
another big patch and automate these updates :)

-- Steve



      reply	other threads:[~2007-03-14  0:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070313204458.531339803@goodmis.org>
     [not found] ` <1173820977.28042.13.camel@localhost.localdomain>
2007-03-13 21:32   ` Linus Torvalds
2007-03-14  0:51     ` Steven Rostedt [this message]

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=1173833497.30118.8.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=ak@muc.de \
    --cc=akpm@linux-foundation.org \
    --cc=chrisw@sous-sol.org \
    --cc=glommer@gmail.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --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

all inboxes | Powered by JetHome®