public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.aribaud@free.fr>
To: rae l <crquan@gmail.com>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	cscope-devel@lists.sourceforge.net
Subject: Re: some problems with latest cscope-15.6, the better way to generate cscope database change
Date: Mon, 04 Aug 2008 08:49:22 +0200	[thread overview]
Message-ID: <4896A672.2050400@free.fr> (raw)
In-Reply-To: <91b13c310808031851v2ca9923fuf543eb4fe9c92e2b@mail.gmail.com>

rae l a écrit :
> From: Denis ChengRq <crquan@gmail.com>
> 
> It's a problem about cscope target of kernel Makefile, and the cscope
> plugin of emacs:
> 1. `make cscope` will generate cscope.files cscope.{in,po,}.out;
> 2. the cscope plugin expect a cscope.out.{in,po,};
> 3. the default `cscope -b` would generate cscope.{in,po,}.out;
> 
> There are three approach to solve it:
> 1. modify the cscope C code;
> 2. modify the cscope emacs plugin lisp code;
> 3. modify the Makefile;
> 
> I have tried to communicate with the cscope upstream, but later I
> realize the third approach is most meaningful.

Er... If the plugin differs from the 'original' code, then I would tend to 
think that the plugin must be fixed, mustn't it? Because there might be 
other apps out there apart from the makefile and plugin which use 
cscope.po.out rather than cscope.out.po, so changing cscope would break 
lots of things. And changing the Makefile will make it only work with the 
plugin but would break other cscope-related apps.

Amicalement,
-- 
Albert.

      reply	other threads:[~2008-08-04  6:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04  1:51 some problems with latest cscope-15.6, the better way to generate cscope database change rae l
2008-08-04  6:49 ` Albert ARIBAUD [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=4896A672.2050400@free.fr \
    --to=albert.aribaud@free.fr \
    --cc=crquan@gmail.com \
    --cc=cscope-devel@lists.sourceforge.net \
    --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