From: Andreas Schwab <schwab@linux-m68k.org>
To: Tom de Vries <tdevries@suse.de>
Cc: Pedro Alves <palves@redhat.com>, Tom Tromey <tom@tromey.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Move gnulib to top level
Date: Fri, 21 Jun 2019 13:23:00 -0000 [thread overview]
Message-ID: <87k1dfoyww.fsf@igel.home> (raw)
In-Reply-To: <777f0d31-6cf5-cd98-8411-c965c9a7dc9f@suse.de> (Tom de Vries's message of "Wed, 19 Jun 2019 17:56:01 +0200")
Committed as obvious.
Andreas.
[PATCH] Add gnulib to gdb release tarball
* src-release.sh (GDB_SUPPORT_DIRS): Add gnulib.
---
ChangeLog | 4 ++++
src-release.sh | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/ChangeLog b/ChangeLog
index c2d02749d6..1b7f860627 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2019-06-21 Andreas Schwab <schwab@linux-m68k.org>
+
+ * src-release.sh (GDB_SUPPORT_DIRS): Add gnulib.
+
2019-06-14 Tom Tromey <tom@tromey.com>
* MAINTAINERS: Add gnulib.
diff --git a/src-release.sh b/src-release.sh
index e1dcd82746..1654656146 100755
--- a/src-release.sh
+++ b/src-release.sh
@@ -311,7 +311,7 @@ gas_release()
tar_compress $package $tool "$GAS_SUPPORT_DIRS" "$compressors"
}
-GDB_SUPPORT_DIRS="bfd include libiberty opcodes readline sim intl libdecnumber cpu zlib contrib"
+GDB_SUPPORT_DIRS="bfd include libiberty opcodes readline sim intl libdecnumber cpu zlib contrib gnulib"
gdb_release()
{
compressors=$1
--
2.22.0
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2019-06-21 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 12:48 Tom Tromey
2019-06-13 13:29 ` Pedro Alves
2019-06-13 18:34 ` Tom Tromey
2019-06-14 19:02 ` Tom Tromey
2019-06-19 15:56 ` Tom de Vries
2019-06-21 13:00 ` Tom Tromey
2019-06-21 13:23 ` Andreas Schwab [this message]
2019-06-21 14:56 ` Tom Tromey
2019-07-30 18:20 ` in-src-tree build regression [Re: [PATCH] Move gnulib to top level] Jan Kratochvil
2019-07-31 17:30 ` Tom Tromey
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=87k1dfoyww.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tdevries@suse.de \
--cc=tom@tromey.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