From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 025e1fe146c254ddba14cddb02210d0d653cd676
Date: Thu, 06 Jul 2017 17:43:09 +0100 [thread overview]
Message-ID: <20170706164310.352411081DE1@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1581 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 025e1fe146c254ddba14cddb02210d0d653cd676 (commit)
from 62bf80f851159af2176fc80b58f5c2bef246252a (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 025e1fe146c254ddba14cddb02210d0d653cd676
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Jul 6 18:37:44 2017 +0200
flash-images: remove wrong 2nd partition
the new sfdisk seems not able to skip a partition anymore.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
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 121dc11..8ed7f63 100644
--- a/lfs/flash-images
+++ b/lfs/flash-images
@@ -94,6 +94,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
# Write Partition table
echo -e "$(S_OFFSET),$(S_BOOT),$(PART_TYPE),*\n,0,0\n$$(( $(S_BOOT) + $(S_OFFSET) )),$(S_ROOT),L\n" \
| sfdisk -uS $(DEVICE)
+ -echo -e "d\n2\nw\n\q\n" | fdisk $(DEVICE)
kpartx -v -a $(DEVICE)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-07-06 16:43 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=20170706164310.352411081DE1@git01.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