public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 16bd7e43c1574fdef0f7729bdfc4928baf084d12
Date: Mon, 26 Aug 2019 11:13:39 +0100	[thread overview]
Message-ID: <20190826101340.62A4F60B08@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2863 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  16bd7e43c1574fdef0f7729bdfc4928baf084d12 (commit)
      from  07a67eed52944e377d4346c6941c9106c83ab291 (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 16bd7e43c1574fdef0f7729bdfc4928baf084d12
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Mon Aug 26 10:12:56 2019 +0000

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

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

Summary of changes:
 config/rootfiles/common/aarch64/rpi-firmware | 7 ++++---
 config/rootfiles/common/aarch64/stage2       | 5 +++--
 2 files changed, 7 insertions(+), 5 deletions(-)

Difference in files:
diff --git a/config/rootfiles/common/aarch64/rpi-firmware b/config/rootfiles/common/aarch64/rpi-firmware
index 6d0f5d434..d8de46b5a 100644
--- a/config/rootfiles/common/aarch64/rpi-firmware
+++ b/config/rootfiles/common/aarch64/rpi-firmware
@@ -10,9 +10,10 @@ boot/start.elf
 boot/start_cd.elf
 boot/start_db.elf
 boot/start_x.elf
-lib/firmware/brcm/brcmfmac43430-sdio.bin
+lib/firmware/brcm/brcmfmac43430-sdio.RPI3.txt
 lib/firmware/brcm/brcmfmac43430-sdio.txt
-lib/firmware/brcm/brcmfmac43430a0-sdio.bin
-lib/firmware/brcm/brcmfmac43455-sdio.bin
 lib/firmware/brcm/brcmfmac43455-sdio.clm_blob
 lib/firmware/brcm/brcmfmac43455-sdio.txt
+lib/firmware/brcm/brcmfmac43430-sdio.bin
+lib/firmware/brcm/brcmfmac43430a0-sdio.bin
+lib/firmware/brcm/brcmfmac43455-sdio.bin
diff --git a/config/rootfiles/common/aarch64/stage2 b/config/rootfiles/common/aarch64/stage2
index 576d3f77b..207448d5d 100644
--- a/config/rootfiles/common/aarch64/stage2
+++ b/config/rootfiles/common/aarch64/stage2
@@ -41,6 +41,7 @@ etc/profile.d/term256.sh
 etc/profile.d/umask.sh
 etc/resolv.conf
 etc/securetty
+#etc/sysctl-x86_64.conf
 etc/sysctl.conf
 etc/syslog.conf
 etc/system-release
@@ -66,7 +67,6 @@ root/.bash_logout
 root/.bash_profile
 root/.bashrc
 root/ipfire
-run
 #sbin
 #srv
 #usr/bin
@@ -106,7 +106,6 @@ usr/local/bin/timecheck
 usr/local/bin/timezone-transition
 usr/local/bin/update-ids-ruleset
 usr/local/bin/update-lang-cache
-usr/local/bin/xt_geoip_build
 usr/local/bin/xt_geoip_update
 #usr/local/include
 #usr/local/lib
@@ -171,6 +170,8 @@ var/mail
 var/run
 #var/spool
 var/tmp
+run
+usr/local/bin/xt_geoip_build
 dev/console
 dev/null
 tmp


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

                 reply	other threads:[~2019-08-26 10:13 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=20190826101340.62A4F60B08@people01.haj.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