From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 906d293b05874db62532b35b10e3fe2b8784c361
Date: Thu, 27 Feb 2014 12:47:42 +0100 [thread overview]
Message-ID: <20140227114742.E97DD20C24@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1460 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 906d293b05874db62532b35b10e3fe2b8784c361 (commit)
from b3aa7a123136f35392cea2d37c91ffce1f416094 (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 906d293b05874db62532b35b10e3fe2b8784c361
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Feb 27 12:46:14 2014 +0100
flash-images: work around a pandaboard uboot bug.
uboot does not find the kernel if it was copied to late to the
fat partition.
-----------------------------------------------------------------------
Summary of changes:
lfs/flash-images | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/lfs/flash-images b/lfs/flash-images
index 822124a..f74c7e1 100644
--- a/lfs/flash-images
+++ b/lfs/flash-images
@@ -102,6 +102,7 @@ endif
ifeq "$(MACHINE_TYPE)" "arm"
cp -v /boot/MLO $(MNThdd)/boot/
cp -v /boot/u-boot.img $(MNThdd)/boot/
+ cp -v /boot/zImage-ipfire-multi $(MNThdd)/boot/
sync
umount $(MNThdd)/boot
mount -o loop $(IMGboot) $(MNThdd)/boot
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-02-27 11:47 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=20140227114742.E97DD20C24@argus.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