From: Harvey Harrison <harvey.harrison@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Len Brown <lenb@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org,
Linux Power Management List <linux-pm@lists.osdl.org>
Subject: Re: git mv (was Re: [git pull] ACPI & Suspend patches for 2.6.29-rc0)
Date: Fri, 09 Jan 2009 13:47:16 -0800 [thread overview]
Message-ID: <1231537636.5726.4.camel@brick> (raw)
In-Reply-To: <20090109212757.GA25434@uranus.ravnborg.org>
On Fri, 2009-01-09 at 22:27 +0100, Sam Ravnborg wrote:
> What other ways exist so I can see what the heck davem did to
> arch/sparc64/kernel/irq.c then?
>
> I know he added IRQ stacks - but how did the patch look like?
> I know no other way to find the old history than to do:
>
> git log --follow arch/sparc/kernel/irq_64.c
>
> But this also give me what I want. I'm just curious if there is
> a better way - in the case where you know the old name.
In that specific case you could just do:
gitk -- name1 name2
And that might be closer to what you're looking for.
Harvey
next prev parent reply other threads:[~2009-01-09 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 10:55 [git pull] ACPI & Suspend patches for 2.6.29-rc0 Len Brown
2009-01-09 20:12 ` Linus Torvalds
2009-01-09 20:56 ` git mv (was Re: [git pull] ACPI & Suspend patches for 2.6.29-rc0) Len Brown
2009-01-09 21:16 ` Linus Torvalds
2009-01-09 21:27 ` Sam Ravnborg
2009-01-09 21:40 ` Linus Torvalds
2009-01-09 21:47 ` Harvey Harrison [this message]
2009-01-09 21:58 ` Linus Torvalds
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=1231537636.5726.4.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=sam@ravnborg.org \
--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