From: Dave Jones <davej@redhat.com>
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>,
Linus Torvalds <torvalds@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 16:01:40 -0400 [thread overview]
Message-ID: <20071015200140.GB20467@redhat.com> (raw)
In-Reply-To: <86802c440710151245s7d12a45fpfdaa041546d965e@mail.gmail.com>
On Mon, Oct 15, 2007 at 12:45:27PM -0700, 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?
add --follow to your command line
> 2. cscope
> on x86_64, it is good to see file in arch/x86/pci/*
> but will show other _32.c too.
> So is it possible to change find-sources to make filter out _32.* and
> mach-* dirs?
I see this as a positive thing personally. You could regenerate the
cscope files by hand. Or maybe introduce a 'cscope_minimal' Makefile
target perhaps.
Dave
--
http://www.codemonkey.org.uk
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 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
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 [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=20071015200140.GB20467@redhat.com \
--to=davej@redhat.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.