From: Tom Tromey <tom@tromey.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Joel Brobecker <brobecker@adacore.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
binutils@sourceware.org
Subject: Re: [PATCH] Add "contrib" to the list of GDB support dirs (on src-release.sh)
Date: Thu, 13 Sep 2018 14:26:00 -0000 [thread overview]
Message-ID: <87h8itqxri.fsf@tromey.com> (raw)
In-Reply-To: <20180912052059.12729-1-sergiodj@redhat.com> (Sergio Durigan Junior's message of "Wed, 12 Sep 2018 01:20:59 -0400")
>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
Sergio> ChangeLog:
Sergio> 2018-09-12 Sergio Durigan Junior <sergiodj@redhat.com>
Sergio> * src-release.sh (GDB_SUPPORT_DIRS): Add "contrib".
Thanks, this is ok.
Tom
next prev parent reply other threads:[~2018-09-13 14:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 11:02 Update dg-extract-results.* from gcc Rainer Orth
2018-07-25 19:08 ` Tom Tromey
2018-07-26 20:54 ` Sergio Durigan Junior
2018-07-31 12:46 ` Rainer Orth
2018-07-31 12:44 ` Rainer Orth
2018-08-06 13:50 ` Rainer Orth
2018-08-07 11:52 ` Rainer Orth
2018-08-07 14:35 ` Pedro Alves
2018-08-08 14:36 ` Rainer Orth
2018-08-08 15:24 ` Pedro Alves
2018-10-01 9:36 ` dg-extract-results's bad sorting behavior (Re: Update dg-extract-results.* from gcc) Pedro Alves
2018-09-11 11:02 ` [obv] Fix dg-extract-results.sh path [Re: Update dg-extract-results.* from gcc] Jan Kratochvil
2018-09-11 11:03 ` Missing toplevel contrib/ in gdb-*.tar.xz " Jan Kratochvil
2018-09-11 11:20 ` Rainer Orth
2018-09-11 12:01 ` Joel Brobecker
2018-09-12 5:21 ` [PATCH] Add "contrib" to the list of GDB support dirs (on src-release.sh) Sergio Durigan Junior
2018-09-13 14:26 ` Tom Tromey [this message]
2018-09-13 16:35 ` Sergio Durigan Junior
2018-09-12 5:23 ` Missing toplevel contrib/ in gdb-*.tar.xz [Re: Update dg-extract-results.* from gcc] 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=87h8itqxri.fsf@tromey.com \
--to=tom@tromey.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=ro@cebitec.uni-bielefeld.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).