public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@redhat.com>
To: Jeff Law <law@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: PING: Re: [patch] tag ../include/*
Date: Mon, 13 Oct 2014 17:30:00 -0000	[thread overview]
Message-ID: <543C0C0A.3020508@redhat.com> (raw)
In-Reply-To: <543BFD55.4080707@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 326 bytes --]

On 10/13/14 09:27, Jeff Law wrote:
> On 10/13/14 08:53, Aldy Hernandez wrote:
>> PING
>>
>> On 10/07/14 09:37, Aldy Hernandez wrote:
>>> Is there a reason we don't create etags for toplevel include files?  If
>>> not, could I please apply this patch?
> ENOPATCH
>
> jeff

Sorry, patch was in original message.  Attached here.

[-- Attachment #2: curr --]
[-- Type: text/plain, Size: 816 bytes --]

commit a679529d14f005d8c88517f72d2b5295d8c82f0f
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Tue Oct 7 09:32:21 2014 -0700

    	* Makefile.in (TAGS): Tag ../include files.

diff --git a/gcc/Makefile.in b/gcc/Makefile.in
index 97b439a..df43b9c 100644
--- a/gcc/Makefile.in
+++ b/gcc/Makefile.in
@@ -3772,6 +3772,7 @@ TAGS: lang.tags
 	  fi;						\
 	done;						\
 	etags -o TAGS.sub c-family/*.h c-family/*.c *.h *.c *.cc \
+	      ../include/*.h \
 	      --language=none --regex="/\(char\|unsigned int\|int\|bool\|void\|HOST_WIDE_INT\|enum [A-Za-z_0-9]+\) [*]?\([A-Za-z_0-9]+\)/\2/" common.opt	\
 	      --language=none --regex="/\(DEF_RTL_EXPR\|DEFTREECODE\|DEFGSCODE\).*(\([A-Za-z_0-9]+\)/\2/" rtl.def tree.def gimple.def \
 	      --language=none --regex="/DEFTIMEVAR (\([A-Za-z_0-9]+\)/\1/" timevar.def \

  reply	other threads:[~2014-10-13 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 16:37 Aldy Hernandez
2014-10-07 19:10 ` Mike Stump
2014-10-13 14:58 ` PING: " Aldy Hernandez
2014-10-13 16:29   ` Jeff Law
2014-10-13 17:30     ` Aldy Hernandez [this message]
2014-10-13 18:43       ` Jeff Law

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=543C0C0A.3020508@redhat.com \
    --to=aldyh@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).