public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [patch] tag ../include/*
@ 2014-10-07 16:37 Aldy Hernandez
  2014-10-07 19:10 ` Mike Stump
  2014-10-13 14:58 ` PING: " Aldy Hernandez
  0 siblings, 2 replies; 6+ messages in thread
From: Aldy Hernandez @ 2014-10-07 16:37 UTC (permalink / raw)
  To: gcc-patches

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

Is there a reason we don't create etags for toplevel include files?  If 
not, could I please apply this patch?

Thanks.
Aldy

[-- 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 \

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [patch] tag ../include/*
  2014-10-07 16:37 [patch] tag ../include/* Aldy Hernandez
@ 2014-10-07 19:10 ` Mike Stump
  2014-10-13 14:58 ` PING: " Aldy Hernandez
  1 sibling, 0 replies; 6+ messages in thread
From: Mike Stump @ 2014-10-07 19:10 UTC (permalink / raw)
  To: Aldy Hernandez; +Cc: gcc-patches

On Oct 7, 2014, at 9:37 AM, Aldy Hernandez <aldyh@redhat.com> wrote:
> Is there a reason we don't create etags for toplevel include files?

I don’t think there is.

>  If not, could I please apply this patch?

I’m in favor.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* PING: Re: [patch] tag ../include/*
  2014-10-07 16:37 [patch] tag ../include/* Aldy Hernandez
  2014-10-07 19:10 ` Mike Stump
@ 2014-10-13 14:58 ` Aldy Hernandez
  2014-10-13 16:29   ` Jeff Law
  1 sibling, 1 reply; 6+ messages in thread
From: Aldy Hernandez @ 2014-10-13 14:58 UTC (permalink / raw)
  To: gcc-patches

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?
>
> Thanks.
> Aldy

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PING: Re: [patch] tag ../include/*
  2014-10-13 14:58 ` PING: " Aldy Hernandez
@ 2014-10-13 16:29   ` Jeff Law
  2014-10-13 17:30     ` Aldy Hernandez
  0 siblings, 1 reply; 6+ messages in thread
From: Jeff Law @ 2014-10-13 16:29 UTC (permalink / raw)
  To: Aldy Hernandez, gcc-patches

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PING: Re: [patch] tag ../include/*
  2014-10-13 16:29   ` Jeff Law
@ 2014-10-13 17:30     ` Aldy Hernandez
  2014-10-13 18:43       ` Jeff Law
  0 siblings, 1 reply; 6+ messages in thread
From: Aldy Hernandez @ 2014-10-13 17:30 UTC (permalink / raw)
  To: Jeff Law, gcc-patches

[-- 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 \

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PING: Re: [patch] tag ../include/*
  2014-10-13 17:30     ` Aldy Hernandez
@ 2014-10-13 18:43       ` Jeff Law
  0 siblings, 0 replies; 6+ messages in thread
From: Jeff Law @ 2014-10-13 18:43 UTC (permalink / raw)
  To: Aldy Hernandez, gcc-patches

On 10/13/14 11:29, Aldy Hernandez wrote:
> 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.
Ok for the trunk.  Sorry it got dropped.
jeff

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2014-10-13 18:38 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-10-07 16:37 [patch] tag ../include/* 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
2014-10-13 18:43       ` Jeff Law

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).