From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 2fcfe2e1f339c868b5800b61433c803023686371
Date: Wed, 29 Jun 2022 18:34:31 +0000 [thread overview]
Message-ID: <4LY99M71yLz2y2v@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1637 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 2fcfe2e1f339c868b5800b61433c803023686371 (commit)
from 636cf631c925a1492ad49edbc69e5dac32927eda (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 2fcfe2e1f339c868b5800b61433c803023686371
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Jun 29 18:34:01 2022 +0000
core169: Add initramdisks for armv6l, too
Looks like I have been ahead of time.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/159 => core/169}/filelists/armv6l/linux-initrd | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/159 => core/169}/filelists/armv6l/linux-initrd (100%)
Difference in files:
diff --git a/config/rootfiles/core/169/filelists/armv6l/linux-initrd b/config/rootfiles/core/169/filelists/armv6l/linux-initrd
new file mode 120000
index 000000000..4af11bfa1
--- /dev/null
+++ b/config/rootfiles/core/169/filelists/armv6l/linux-initrd
@@ -0,0 +1 @@
+../../../../common/armv6l/linux-initrd
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-06-29 18:34 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=4LY99M71yLz2y2v@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