From: Michal Marek <mmarek@suse.cz>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: linux-kbuild@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: specify absolute paths for cscope
Date: Mon, 30 Nov 2009 18:13:47 +0100 [thread overview]
Message-ID: <4B13FD4B.5080805@suse.cz> (raw)
In-Reply-To: <1259238852-21214-1-git-send-email-daniel.vetter@ffwll.ch>
On 26.11.2009 13:34, Daniel Vetter wrote:
> Some tools (like my favourite editor, vim) can't handle relative
> paths from cscope as soon as cscope.out is no longer in $PWD. Use
> absolute paths when generating cscope.files, which seems to be
> the recommended way to generate cscope.out, anyway (at least according
> to cscope.sf.net).
But it will fail if you rename the source directory. I'm not sure what
is worse, I myself don't use cscope much. Fixing vim would be the ideal
solution of course (it already handles ../tags fine).
Michal
next prev parent reply other threads:[~2009-11-30 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 12:34 [PATCH] kbuild: specify absolute paths for cscope Daniel Vetter
2009-11-30 17:13 ` Michal Marek [this message]
2009-11-30 18:11 ` Sam Ravnborg
2009-12-01 9:42 ` Daniel Vetter
2009-12-01 13:06 ` Michal Marek
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=4B13FD4B.5080805@suse.cz \
--to=mmarek@suse.cz \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).