From: Nick Clifton <nickc@redhat.com>
To: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Commit: Add multilib.am to src-release.sh's list of top level files
Date: Fri, 19 Jan 2024 11:44:31 +0000 [thread overview]
Message-ID: <875xzplf8g.fsf@redhat.com> (raw)
Hi Guys,
I am applying the patch below to add multilib.am to src-release.sh's
list of top level files that should be included in any release. This
file is needed when rebuilding the Makefiles in the libbacktrace and
zlib sub-directories.
Cheers
Nick
diff --git a/src-release.sh b/src-release.sh
index bc947ebc56f..169135856a2 100755
--- a/src-release.sh
+++ b/src-release.sh
@@ -45,7 +45,8 @@ DEVO_SUPPORT="ar-lib ChangeLog compile config config-ml.in config.guess \
ltmain.sh ltoptions.m4 ltsugar.m4 ltversion.m4 lt~obsolete.m4 \
MAINTAINERS Makefile.def Makefile.in Makefile.tpl missing mkdep \
mkinstalldirs move-if-change README README-maintainer-mode \
- SECURITY.txt src-release.sh symlink-tree test-driver ylwrap"
+ SECURITY.txt src-release.sh symlink-tree test-driver ylwrap \
+ multilib.am"
# Files in devo/etc used in any net release.
ETC_SUPPORT="Makefile.in configure configure.in standards.texi \
reply other threads:[~2024-01-19 11:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=875xzplf8g.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.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).