public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e07760a24bbff90a140a6dd3781b0c43f4d2a62d
Date: Thu, 17 Sep 2015 13:14:21 +0200	[thread overview]
Message-ID: <20150917111421.CE569223AD@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2882 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  e07760a24bbff90a140a6dd3781b0c43f4d2a62d (commit)
      from  7f16eac4a40f843002bbcb3a19654689438ffe1b (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 e07760a24bbff90a140a6dd3781b0c43f4d2a62d
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Thu Sep 17 13:13:19 2015 +0200

    binutils: rootfile update.
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/common/i586/binutils | 39 +++++++++++++++++++++++++++++++++++
 1 file changed, 39 insertions(+)

Difference in files:
diff --git a/config/rootfiles/common/i586/binutils b/config/rootfiles/common/i586/binutils
index 48f20e9..d0997bf 100644
--- a/config/rootfiles/common/i586/binutils
+++ b/config/rootfiles/common/i586/binutils
@@ -47,6 +47,45 @@
 #usr/lib/ldscripts/elf_i386.xsw
 #usr/lib/ldscripts/elf_i386.xu
 #usr/lib/ldscripts/elf_i386.xw
+#usr/lib/ldscripts/elf_k1om.x
+#usr/lib/ldscripts/elf_k1om.xbn
+#usr/lib/ldscripts/elf_k1om.xc
+#usr/lib/ldscripts/elf_k1om.xd
+#usr/lib/ldscripts/elf_k1om.xdc
+#usr/lib/ldscripts/elf_k1om.xdw
+#usr/lib/ldscripts/elf_k1om.xn
+#usr/lib/ldscripts/elf_k1om.xr
+#usr/lib/ldscripts/elf_k1om.xs
+#usr/lib/ldscripts/elf_k1om.xsc
+#usr/lib/ldscripts/elf_k1om.xsw
+#usr/lib/ldscripts/elf_k1om.xu
+#usr/lib/ldscripts/elf_k1om.xw
+#usr/lib/ldscripts/elf_l1om.x
+#usr/lib/ldscripts/elf_l1om.xbn
+#usr/lib/ldscripts/elf_l1om.xc
+#usr/lib/ldscripts/elf_l1om.xd
+#usr/lib/ldscripts/elf_l1om.xdc
+#usr/lib/ldscripts/elf_l1om.xdw
+#usr/lib/ldscripts/elf_l1om.xn
+#usr/lib/ldscripts/elf_l1om.xr
+#usr/lib/ldscripts/elf_l1om.xs
+#usr/lib/ldscripts/elf_l1om.xsc
+#usr/lib/ldscripts/elf_l1om.xsw
+#usr/lib/ldscripts/elf_l1om.xu
+#usr/lib/ldscripts/elf_l1om.xw
+#usr/lib/ldscripts/elf_x86_64.x
+#usr/lib/ldscripts/elf_x86_64.xbn
+#usr/lib/ldscripts/elf_x86_64.xc
+#usr/lib/ldscripts/elf_x86_64.xd
+#usr/lib/ldscripts/elf_x86_64.xdc
+#usr/lib/ldscripts/elf_x86_64.xdw
+#usr/lib/ldscripts/elf_x86_64.xn
+#usr/lib/ldscripts/elf_x86_64.xr
+#usr/lib/ldscripts/elf_x86_64.xs
+#usr/lib/ldscripts/elf_x86_64.xsc
+#usr/lib/ldscripts/elf_x86_64.xsw
+#usr/lib/ldscripts/elf_x86_64.xu
+#usr/lib/ldscripts/elf_x86_64.xw
 #usr/lib/ldscripts/i386linux.x
 #usr/lib/ldscripts/i386linux.xbn
 #usr/lib/ldscripts/i386linux.xn


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2015-09-17 11:14 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=20150917111421.CE569223AD@argus.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