public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 4eedf6793b5dc5c6f3d91fb1db0b32a3fc40c24d
Date: Thu, 20 Sep 2018 19:05:53 +0100	[thread overview]
Message-ID: <20180920180554.5CA071081BD3@git01.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2214 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  4eedf6793b5dc5c6f3d91fb1db0b32a3fc40c24d (commit)
      from  bdf9df742caf803272f7a34cadc9d7dc4ea17a78 (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 4eedf6793b5dc5c6f3d91fb1db0b32a3fc40c24d
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Thu Sep 20 20:03:26 2018 +0200

    rebuild-initrd: update for grub2
    
    this was was not used for years because we usually ship a prebuild ramdisk
    so this incompatiblity was not noticed long time...
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 src/scripts/rebuild-initrd | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Difference in files:
diff --git a/src/scripts/rebuild-initrd b/src/scripts/rebuild-initrd
index 91e68ca57..3dd08dc21 100644
--- a/src/scripts/rebuild-initrd
+++ b/src/scripts/rebuild-initrd
@@ -17,11 +17,11 @@
 # along with IPFire; if not, write to the Free Software                    #
 # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307 USA #
 #                                                                          #
-# Copyright (C) 2008 IPFire-Team <info(a)ipfire.org>.                        #
+# Copyright (C) 2018 IPFire-Team <info(a)ipfire.org>.                        #
 #                                                                          #
 ############################################################################
 #
 #
-KVER=`uname -r | cut -d"-" -f1`
+KVER=`uname -r`
 
-dracut --force --early-microcode --verbose /boot/ipfirerd-$KVER.img $KVER-ipfire
+dracut --force --early-microcode --xz /boot/initramfs-$KVER.img $KVER


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2018-09-20 18:05 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=20180920180554.5CA071081BD3@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