From: Jeff Law <jeffreyalaw@gmail.com>
To: Eric Gallager <egall@gwmail.gwu.edu>, Jeff Law <law@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Allow `make tags` to work from top-level directory
Date: Tue, 12 Oct 2021 07:18:04 -0600 [thread overview]
Message-ID: <98b7d7ad-3869-f44f-c95c-289da8cb2828@gmail.com> (raw)
In-Reply-To: <CAMfHzOsJ=SWNVzOWJ=t--v3JJTJqu2-vjWe5Xn4osd4BO8M9yA@mail.gmail.com>
On 10/11/2021 4:05 PM, Eric Gallager via Gcc-patches wrote:
> On Thu, Oct 13, 2016 at 4:43 PM Eric Gallager <egall@gwmail.gwu.edu> wrote:
>> On 10/13/16, Jeff Law <law@redhat.com> wrote:
>>> On 10/06/2016 07:21 AM, Eric Gallager wrote:
>>>> The libdecnumber, libgcc, and libobjc subdirectories are missing TAGS
>>>> targets in their Makefiles. The attached patch causes them to be
>>>> skipped when running `make tags`.
>>>>
>>>> ChangeLog entry:
>>>>
>>>> 2016-10-06 Eric Gallager <egall@gwmail.gwu.edu>
>>>>
>>>> * Makefile.def: Mark libdecnumber, libgcc, and libobjc as missing
>>>> TAGS target.
>>>> * Makefile.in: Regenerate.
>>>>
>>> OK. Please install.
>>>
>>> Thanks,
>>> Jeff
>>>
>>
>> I'm still waiting to hear back from <assign@gnu.org> about my request
>> for copyright assignment, which I'll need to get sorted out before I
>> can start committing stuff (like this patch).
>>
>> Thanks,
>> Eric
> Update: In the intervening years, I got my copyright assignment filed
> and have recently become able to commit again; is your old approval
> from 2016 still valid, Jeff, or do I need a re-approval?
> Ref: https://gcc.gnu.org/legacy-ml/gcc-patches/2016-10/msg00370.html
It's still valid. Just re-test and commit.
jeff
next prev parent reply other threads:[~2021-10-12 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 13:21 Eric Gallager
2016-10-13 18:38 ` Jeff Law
2016-10-13 20:44 ` Eric Gallager
2021-10-11 22:05 ` Eric Gallager
2021-10-12 13:18 ` Jeff Law [this message]
2021-10-12 19:56 ` Eric Gallager
2021-10-12 21:03 ` Eric Gallager
2021-10-14 16:26 ` 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=98b7d7ad-3869-f44f-c95c-289da8cb2828@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=egall@gwmail.gwu.edu \
--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).