From: Tom Tromey <tom@tromey.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add libctf to src-release.sh:GDB_SUPPORT_DIRS
Date: Thu, 17 Oct 2019 16:54:00 -0000 [thread overview]
Message-ID: <87v9snmhxo.fsf@tromey.com> (raw)
In-Reply-To: <20191016205022.30613-1-sergiodj@redhat.com> (Sergio Durigan Junior's message of "Wed, 16 Oct 2019 16:50:22 -0400")
>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
Sergio> We're forgetting to include the libctf directory when creating the
Sergio> snapshot. This commit changes src-release.sh and adds it to
Sergio> GDB_SUPPORT_DIRS.
Sergio> 2019-10-16 Sergio Durigan Junior <sergiodj@redhat.com>
Sergio> * src-release.sh (GDB_SUPPORT_DIRS): Add libctf.
Thanks, this is ok.
Tom
next prev parent reply other threads:[~2019-10-17 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 20:50 Sergio Durigan Junior
2019-10-17 16:54 ` Tom Tromey [this message]
2019-10-17 18:01 ` Sergio Durigan Junior
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=87v9snmhxo.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@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