public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 1ca8bd7aa2cdb9311aa2d6d75e4fce55a1b91e18
Date: Thu, 10 Jun 2021 18:01:17 +0000	[thread overview]
Message-ID: <4G1BcG0Ck7z2xLX@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2878 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, master has been updated
       via  1ca8bd7aa2cdb9311aa2d6d75e4fce55a1b91e18 (commit)
      from  abd5cc3cb758bc63b9c9d0a08812991fcfaf71b5 (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 1ca8bd7aa2cdb9311aa2d6d75e4fce55a1b91e18
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Thu Jun 10 18:01:00 2021 +0000

    core157: Fix shipping boost
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

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

Summary of changes:
 config/rootfiles/{oldcore/151 => core/157}/filelists/armv5tel/boost | 0
 config/rootfiles/core/157/filelists/boost                           | 1 -
 config/rootfiles/{oldcore/151 => core/157}/filelists/i586/boost     | 0
 config/rootfiles/{oldcore/151 => core/157}/filelists/x86_64/boost   | 0
 4 files changed, 1 deletion(-)
 copy config/rootfiles/{oldcore/151 => core/157}/filelists/armv5tel/boost (100%)
 delete mode 120000 config/rootfiles/core/157/filelists/boost
 copy config/rootfiles/{oldcore/151 => core/157}/filelists/i586/boost (100%)
 copy config/rootfiles/{oldcore/151 => core/157}/filelists/x86_64/boost (100%)

Difference in files:
diff --git a/config/rootfiles/core/157/filelists/armv5tel/boost b/config/rootfiles/core/157/filelists/armv5tel/boost
new file mode 120000
index 000000000..bb17e08d6
--- /dev/null
+++ b/config/rootfiles/core/157/filelists/armv5tel/boost
@@ -0,0 +1 @@
+../../../../common/armv5tel/boost
\ No newline at end of file
diff --git a/config/rootfiles/core/157/filelists/boost b/config/rootfiles/core/157/filelists/boost
deleted file mode 120000
index 05246f07c..000000000
--- a/config/rootfiles/core/157/filelists/boost
+++ /dev/null
@@ -1 +0,0 @@
-../../../common/boost
\ No newline at end of file
diff --git a/config/rootfiles/core/157/filelists/i586/boost b/config/rootfiles/core/157/filelists/i586/boost
new file mode 120000
index 000000000..3ff5a3be4
--- /dev/null
+++ b/config/rootfiles/core/157/filelists/i586/boost
@@ -0,0 +1 @@
+../../../../common/i586/boost
\ No newline at end of file
diff --git a/config/rootfiles/core/157/filelists/x86_64/boost b/config/rootfiles/core/157/filelists/x86_64/boost
new file mode 120000
index 000000000..9ed31e1d5
--- /dev/null
+++ b/config/rootfiles/core/157/filelists/x86_64/boost
@@ -0,0 +1 @@
+../../../../common/x86_64/boost
\ No newline at end of file


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

                 reply	other threads:[~2021-06-10 18:01 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=4G1BcG0Ck7z2xLX@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