summaryrefslogtreecommitdiff
path: root/Kbuild
diff options
context:
space:
mode:
authorMichal Marek <mmarek@suse.cz>2010-03-08 10:26:22 +0100
committerMichal Marek <mmarek@suse.cz>2010-03-08 10:26:22 +0100
commite93bc1a0cab3e54e3c1947e01c8e73892e35630d (patch)
treef7b40bb868ad3a4e1895a5a0cca82a5c08300c2a /Kbuild
parenta6c366324cacd5f71107dd01362b995a1c67b1ad (diff)
Revert "kbuild: specify absolute paths for cscope"
This reverts commit eb8f844c0a41c4529a7d06b7801296eca9ae67aa. Ian Campbell writes: > I keep my kernel source tree on a more powerful build box where I run my > builds etc (including "make cscope") but run my editor from my > workstation with an NFS mount to the source. This worked fine for me > using relative paths for cscope. Using absolute paths in cscope breaks > this previously working setup because the root path is not the same on > both systems. I guess this is similar to moving the source tree around. > > Without wanting to start a flamewar it really sounds to me like we are > working around a vim (or cscope) bug here, emacs with cscope bindings > works fine in this configuration. Given that absolute paths can be forced by make O=. cscope, change the default back to relative paths. Ian Campbell <ijc@hellion.org.uk> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Michal Marek <mmarek@suse.cz>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions