From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 16b499c4b98271c10436dc910f109c97b8e6df31
Date: Tue, 07 Apr 2020 09:15:39 +0000 [thread overview]
Message-ID: <48xMFl57V0z2xwT@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1639 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 16b499c4b98271c10436dc910f109c97b8e6df31 (commit)
from 21be3871b9ac2ca3d5d744c22890f55cdf334006 (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 16b499c4b98271c10436dc910f109c97b8e6df31
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Apr 7 11:15:03 2020 +0200
pcengines-apu-firmware: fix lfs file
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/pcengines-apu-firmware | 5 -----
1 file changed, 5 deletions(-)
Difference in files:
diff --git a/lfs/pcengines-apu-firmware b/lfs/pcengines-apu-firmware
index e430ad9a2..0eef1d510 100644
--- a/lfs/pcengines-apu-firmware
+++ b/lfs/pcengines-apu-firmware
@@ -96,8 +96,3 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
/lib/firmware/pcengines/apu
@$(POSTBUILD)
-eb9513cdb9bb212db524307d71d9f87c cache/apu1_v4.11.0.5.rom
-e3ce78e1cbc1eb35b10d97349afabf04 cache/apu2_v4.11.0.5.rom
-42ece2873efc4a4b86bb507df40423c6 cache/apu3_v4.11.0.5.rom
-e5eb7a15efbfc1a434d3bd48d1bc5062 cache/apu4_v4.11.0.5.rom
-f2924f98bbb1e2816760103ab045a175 cache/apu5_v4.11.0.5.rom
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-04-07 9:15 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=48xMFl57V0z2xwT@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