mv kernel/acpi/processor.c
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 2 lines · Steven Rostedt
Move
kernel/acpi/processor.cto 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
Quoted 8 lines · Linus Torvalds
Quoted 2 lines · Steven Rostedt
Move
kernel/acpi/processor.cto 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.
Quoted 8 lines
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.
Quoted 4 lines
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