From: Ian Campbell <ijc@hellion.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Jim Radford <radford@galvanix.net>
Subject: Re: [RFC PATCH] kbuild: move tags support to a shell script
Date: Mon, 24 Nov 2008 10:31:08 +0000 [thread overview]
Message-ID: <1227522668.9425.21.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20081122231631.GA6456@uranus.ravnborg.org>
On Sun, 2008-11-23 at 00:16 +0100, Sam Ravnborg wrote:
> As no-one else wanted to do so - I now moved the tags support
> to a shell script of its own.
> The usage is the same: make {tags,TAGS,cscope}
>
> The ALLSOURCE_ARCHS suppport was lost in the transition - is it actually used by anyone?
I'm the one who actually added it way back in
a0674e88d9c150e016a69e78e735f48772314c53 and to be honest I don't use it
anymore since I've changed jobs and only really do x86 now...
I can't say if anyone else is using it though.
> I have given the patch only some light testing.
>
> Could those of you that actually sues tags/cscope plese give it a try.
I tested your second patch from the subsequent email and functionally it
seems fine, it currently includes include/asm-* for all architectures
but I suppose they will all go away shortly.
The output was a bit odd though:
$ make cscope
/bin/sh /local/scratch/ianc/devel/linux-2.6.git/scripts/tags.sh cscope
GEN cscope.out (from 13251 files)
I guess I would have expected " GEN cscope.files" instead of the
first line or just " TAGS"?
Ian.
--
Ian Campbell
Current Noise: Nine Inch Nails - Where Is Everybody?
"We came. We saw. We kicked its ass."
-- Bill Murray, _Ghostbusters_
next prev parent reply other threads:[~2008-11-24 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 23:16 [RFC PATCH] kbuild: move tags support to a shell script Sam Ravnborg
2008-11-23 8:54 ` Sam Ravnborg
2008-11-24 10:31 ` Ian Campbell [this message]
2008-11-24 11:24 ` Sam Ravnborg
2008-11-24 11:33 ` Ian Campbell
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=1227522668.9425.21.camel@zakaz.uk.xensource.com \
--to=ijc@hellion.org.uk \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=radford@galvanix.net \
--cc=sam@ravnborg.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