From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. bbe8e248fe143cfb618eb519dc552fa91858d902
Date: Tue, 20 Feb 2018 20:11:04 +0000 [thread overview]
Message-ID: <20180220201104.9691F106D063@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1519 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 bbe8e248fe143cfb618eb519dc552fa91858d902 (commit)
from ea3b9a4f8837242222115601487259181f79df9d (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 bbe8e248fe143cfb618eb519dc552fa91858d902
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Feb 20 20:10:30 2018 +0000
Rootfile update
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/armv5tel/binutils | 2 --
1 file changed, 2 deletions(-)
Difference in files:
diff --git a/config/rootfiles/common/armv5tel/binutils b/config/rootfiles/common/armv5tel/binutils
index f12527922..c12b90fe2 100644
--- a/config/rootfiles/common/armv5tel/binutils
+++ b/config/rootfiles/common/armv5tel/binutils
@@ -213,5 +213,3 @@ usr/lib/libopcodes-2.30.so
#usr/share/man/man1/strip.1
#usr/share/man/man1/windmc.1
#usr/share/man/man1/windres.1
--usr/lib/libbfd-2.28.so
--usr/lib/libopcodes-2.28.so
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-02-20 20:11 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=20180220201104.9691F106D063@git01.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