public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, stefani@seibold.net
Subject: [PATCH] tags: put function prototypes back!
Date: Wed, 3 Feb 2010 22:18:17 +0200	[thread overview]
Message-ID: <20100203201816.GA5987@x200> (raw)

commit 7db86dc97fb0c47af63e6b965e8ff37126050d25
"ctags: usability fix" removed function prototypes from tags file
claiming "It makes no real sense to include function prototypes".
But it is useful for quickly determining which header file developer
needs to include to fix compilation.

Now if someone wants to remove forward declatations (which I agree are
baggage), write a postprocessing script.

Please apply.

	Alexey, who is sick reverting this chunk locally.

Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
---

 scripts/tags.sh |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/scripts/tags.sh
+++ b/scripts/tags.sh
@@ -108,7 +108,7 @@ exuberant()
 	-I ____cacheline_internodealigned_in_smp                \
 	-I EXPORT_SYMBOL,EXPORT_SYMBOL_GPL                      \
 	-I DEFINE_TRACE,EXPORT_TRACEPOINT_SYMBOL,EXPORT_TRACEPOINT_SYMBOL_GPL \
-	--extra=+f --c-kinds=-px                                \
+	--extra=+f --c-kinds=+px                                \
 	--regex-asm='/^ENTRY\(([^)]*)\).*/\1/'                  \
 	--regex-c='/^SYSCALL_DEFINE[[:digit:]]?\(([^,)]*).*/sys_\1/'
 

             reply	other threads:[~2010-02-03 20:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 20:18 Alexey Dobriyan [this message]
2010-06-15  9:22 ` [PATCH] tags: put function prototypes back! Uwe Kleine-König
2010-06-15  9:54   ` Michal Marek
2010-06-15 11:41     ` Uwe Kleine-König
2010-06-15 11:52       ` Michal Marek
2010-11-04  9:24         ` [RESEND PATCH] " Uwe Kleine-König
2010-11-17  9:06           ` Uwe Kleine-König
2010-12-02 11:53             ` 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=20100203201816.GA5987@x200 \
    --to=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefani@seibold.net \
    --cc=torvalds@linux-foundation.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