From: Linus Torvalds <torvalds@linux-foundation.org>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Andi Kleen <ak@suse.de>, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: git/cscope with x86 merge
Date: Mon, 15 Oct 2007 13:00:38 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0710151256260.6887@woody.linux-foundation.org> (raw)
In-Reply-To: <86802c440710151245s7d12a45fpfdaa041546d965e@mail.gmail.com>
On Mon, 15 Oct 2007, Yinghai Lu wrote:
>
> after the merge:
> 1. git
> git log -p arch/x86/kernel/io_apic_64.c
> only can show the log from the merge..., and can not get log before
> merge for x86_64/kernel/io_apic.c
> Any git update for that?
Use
git log -p --follow arch/x86/kernel/io_apic_64.c
where the "--follow" tells git to follow renames.
And, of course, "git blame -C" will follow renames and copying of code
across file boundaries too.
NOTE! In both cases you may actually have to tell git to not limit its
rename detection when it sees lots of files. You can do that
once-and-for-all with
git config --global diff.renamelimit 0
which should take care of it (although it seems that due to unlucky
timing, the current stable git release does not honor the renamelimit for
merging, so if you actually need to have git merge data across a rename,
you should use the current "master" branch of git. Junio is sadly away
for two weeks right now)
> 2. cscope
No idea on cscope..
Linus
next prev parent reply other threads:[~2007-10-15 20:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 19:45 Yinghai Lu
2007-10-15 20:00 ` Linus Torvalds [this message]
2007-10-20 9:40 ` Yinghai Lu
2007-10-20 15:56 ` Linus Torvalds
2007-10-20 16:47 ` Sam Ravnborg
2007-10-20 17:39 ` Thomas Gleixner
2007-10-20 18:19 ` Linus Torvalds
2007-10-20 18:49 ` Linus Torvalds
2007-10-20 19:15 ` Sam Ravnborg
2007-10-20 19:36 ` Linus Torvalds
2007-10-20 20:10 ` Sam Ravnborg
2007-10-20 20:44 ` Andi Kleen
2007-10-20 21:45 ` Linus Torvalds
2007-10-15 20:01 ` Dave Jones
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=alpine.LFD.0.999.0710151256260.6887@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/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®