From: Mark Frazer <mark@somanetworks.com>
To: Pete Wyckoff <pw@osc.edu>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Makefile patch for cscope and saner Ctags
Date: Thu, 31 May 2001 14:17:28 -0400 [thread overview]
Message-ID: <20010531141728.C28505@somanetworks.com> (raw)
In-Reply-To: <20010530180232.A4546@somanetworks.com> <20010531134530.A15302@osc.edu>
In-Reply-To: <20010531134530.A15302@osc.edu>; from pw@osc.edu on Thu, May 31, 2001 at 01:45:30PM -0400
Pete Wyckoff <pw@osc.edu> [01/05/31 13:56]:
>
> You seem not to have read my response to your earlier mail proprosing
> such a thing (for tags only, not cscope):
>
> http://boudicca.tux.org/hypermail/linux-kernel/2001week21/1869.html
I did. I didn't want to sign up to maintain the ctags-ignore file though.
>
> How does the patch above fix anything? You're sorting so that
> include/linux/*.h comes before include/linux/{mtd,lockd,raid,...}/*.h,
> but I don't see how that can be an improvement, or how it addresses
> your original complaint "ctags doesn't honour any CPP #if'ing".
The sort -s is a stable sort, so by putting things into ctags in the
order I want them to appear in my tags file I get what I want. YMMV
My original complaint ain't gonna get fixed anytime soon.
Your script is definitely a better solution IMO.
-mark
next prev parent reply other threads:[~2001-05-31 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 22:02 Makefile patch for cscope and saner Ctags Mark Frazer
2001-05-31 17:45 ` Pete Wyckoff
2001-05-31 18:17 ` Mark Frazer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-31 16:11 Khachaturov, Vassilii
2001-05-31 18:06 ` Mark Frazer
2001-05-31 18:56 ` george anzinger
2001-05-31 18:52 Khachaturov, Vassilii
2001-05-31 20:44 ` Mark Frazer
2001-06-01 18:39 Khachaturov, Vassilii
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=20010531141728.C28505@somanetworks.com \
--to=mark@somanetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pw@osc.edu \
/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