From: Sam Ravnborg <sam@ravnborg.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>, Andi Kleen <ak@suse.de>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: git/cscope with x86 merge
Date: Sat, 20 Oct 2007 21:15:34 +0200 [thread overview]
Message-ID: <20071020191534.GA8774@uranus.ravnborg.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0710201140550.3794@woody.linux-foundation.org>
On Sat, Oct 20, 2007 at 11:49:51AM -0700, Linus Torvalds wrote:
>
>
> On Sat, 20 Oct 2007, Linus Torvalds wrote:
> >
> > I could perhaps look at making "git log --follow" also break up files that
> > got totally rewritten (git already has a notion of "-B" to do that), but
> > no, we don't do it right now.
>
> Ok, if you guys have a current git source, and want to try something out,
> this fairly small patch does this.
I pulled next branch of git and applied your patch.
When running
git log --follow -B arch/x86/kernel/vmlinux_64.lds.S
I got no output at all (in a newly pulled linux kernel dir).
When I ran
git log arch/x86/kernel/vmlinux_64.lds.S
I got:
commit 250c22777fe1ccd7ac588579a6c16db4c0161cc5
Author: Thomas Gleixner <tglx@linutronix.de>
Date: Thu Oct 11 11:17:24 2007 +0200
x86_64: move kernel
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
With -B alone I got same output.
When I add --follow I get no output.
I could not get back to my previous git binary - I replaced it
with the new one.
cat ~/.gitconfig
[diff]
renamelimit = 0
Sam
next prev parent reply other threads:[~2007-10-20 19:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 19:45 git/cscope with x86 merge Yinghai Lu
2007-10-15 20:00 ` Linus Torvalds
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 [this message]
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=20071020191534.GA8774@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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