From: Mike Stump <mikestump@comcast.net>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] tag ../include/*
Date: Tue, 07 Oct 2014 19:10:00 -0000 [thread overview]
Message-ID: <0362273A-63B1-4A7A-B3A1-EF856A08F8B5@comcast.net> (raw)
In-Reply-To: <543416D2.4050100@redhat.com>
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.
next prev parent reply other threads:[~2014-10-07 19:10 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 [this message]
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
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=0362273A-63B1-4A7A-B3A1-EF856A08F8B5@comcast.net \
--to=mikestump@comcast.net \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).