From: Marcel Lorenz <marcel.lorenz@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] binutils: fix rootfiles after gzip update (check rootfile msg)
Date: Mon, 07 Mar 2016 15:48:39 +0100 [thread overview]
Message-ID: <1457362119-30081-1-git-send-email-marcel.lorenz@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]
Signed-off-by: Marcel Lorenz <marcel.lorenz(a)ipfire.org>
---
config/rootfiles/common/armv5tel/binutils | 1 +
config/rootfiles/common/i586/binutils | 1 +
config/rootfiles/common/x86_64/binutils | 1 +
3 files changed, 3 insertions(+)
diff --git a/config/rootfiles/common/armv5tel/binutils b/config/rootfiles/common/armv5tel/binutils
index ba64237..6fcd5ba 100644
--- a/config/rootfiles/common/armv5tel/binutils
+++ b/config/rootfiles/common/armv5tel/binutils
@@ -60,6 +60,7 @@ usr/lib/libopcodes-2.24.so
#usr/share/info/bfd.info
#usr/share/info/binutils.info
#usr/share/info/configure.info
+#usr/share/info/dir
#usr/share/info/gprof.info
#usr/share/info/ld.info
#usr/share/info/standards.info
diff --git a/config/rootfiles/common/i586/binutils b/config/rootfiles/common/i586/binutils
index fd5bfb8..5f4c113 100644
--- a/config/rootfiles/common/i586/binutils
+++ b/config/rootfiles/common/i586/binutils
@@ -104,6 +104,7 @@ usr/lib/libopcodes-2.24.so
#usr/share/info/bfd.info
#usr/share/info/binutils.info
#usr/share/info/configure.info
+#usr/share/info/dir
#usr/share/info/gprof.info
#usr/share/info/ld.info
#usr/share/info/standards.info
diff --git a/config/rootfiles/common/x86_64/binutils b/config/rootfiles/common/x86_64/binutils
index b1f819c..bb0bf9b 100644
--- a/config/rootfiles/common/x86_64/binutils
+++ b/config/rootfiles/common/x86_64/binutils
@@ -104,6 +104,7 @@
#usr/share/info/bfd.info
#usr/share/info/binutils.info
#usr/share/info/configure.info
+#usr/share/info/dir
#usr/share/info/gprof.info
#usr/share/info/ld.info
#usr/share/info/standards.info
--
1.9.1
reply other threads:[~2016-03-07 14:48 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=1457362119-30081-1-git-send-email-marcel.lorenz@ipfire.org \
--to=marcel.lorenz@ipfire.org \
--cc=development@lists.ipfire.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