From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 28093c8376fb8bd13ce44585fcbed49610093158
Date: Sat, 08 Jun 2019 11:34:53 +0100 [thread overview]
Message-ID: <20190608103453.A99E984FDBF@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 28093c8376fb8bd13ce44585fcbed49610093158 (commit)
from 09b99106962149873a7071931afff75d84fb1ef9 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 28093c8376fb8bd13ce44585fcbed49610093158
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Jun 8 11:34:37 2019 +0100
Rootfile update
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/i586/binutils | 2 --
1 file changed, 2 deletions(-)
Difference in files:
diff --git a/config/rootfiles/common/i586/binutils b/config/rootfiles/common/i586/binutils
index e82fd907c..2d4f12a33 100644
--- a/config/rootfiles/common/i586/binutils
+++ b/config/rootfiles/common/i586/binutils
@@ -306,5 +306,3 @@ usr/lib/libopcodes-2.32.so
#usr/share/man/man1/strip.1
#usr/share/man/man1/windmc.1
#usr/share/man/man1/windres.1
--usr/lib/libbfd-2.30.so
--usr/lib/libopcodes-2.30.so
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-06-08 10:34 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=20190608103453.A99E984FDBF@people01.i.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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