From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 7b0c6a5b3a12535831f1418b9dc5f6385e0c033d
Date: Sat, 17 Apr 2021 10:51:30 +0000 [thread overview]
Message-ID: <4FMqdH0Dnxz2xlD@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2369 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 7b0c6a5b3a12535831f1418b9dc5f6385e0c033d (commit)
from 758565ce8655e33a01cbcdd8ec5daac85b055a9f (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 7b0c6a5b3a12535831f1418b9dc5f6385e0c033d
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Apr 17 10:51:06 2021 +0000
core156: Avoid name collision in rootfiles
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/156/filelists/aarch64/{files => arch-files} | 0
config/rootfiles/core/156/filelists/armv5tel/{files => arch-files} | 0
config/rootfiles/core/156/filelists/x86_64/{files => arch-files} | 0
3 files changed, 0 insertions(+), 0 deletions(-)
rename config/rootfiles/core/156/filelists/aarch64/{files => arch-files} (100%)
rename config/rootfiles/core/156/filelists/armv5tel/{files => arch-files} (100%)
rename config/rootfiles/core/156/filelists/x86_64/{files => arch-files} (100%)
Difference in files:
diff --git a/config/rootfiles/core/156/filelists/aarch64/files b/config/rootfiles/core/156/filelists/aarch64/arch-files
similarity index 100%
rename from config/rootfiles/core/156/filelists/aarch64/files
rename to config/rootfiles/core/156/filelists/aarch64/arch-files
diff --git a/config/rootfiles/core/156/filelists/armv5tel/files b/config/rootfiles/core/156/filelists/armv5tel/arch-files
similarity index 100%
rename from config/rootfiles/core/156/filelists/armv5tel/files
rename to config/rootfiles/core/156/filelists/armv5tel/arch-files
diff --git a/config/rootfiles/core/156/filelists/x86_64/files b/config/rootfiles/core/156/filelists/x86_64/arch-files
similarity index 100%
rename from config/rootfiles/core/156/filelists/x86_64/files
rename to config/rootfiles/core/156/filelists/x86_64/arch-files
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2021-04-17 10:51 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=4FMqdH0Dnxz2xlD@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