public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 4ac89f177dac155aea3f5c8c1fdd308f0977cef6
Date: Thu, 09 Jul 2015 12:41:51 +0200	[thread overview]
Message-ID: <20150709104151.75A9D2239D@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1337 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  4ac89f177dac155aea3f5c8c1fdd308f0977cef6 (commit)
      from  7a007abe918e1ded4ee2fe42428b317ff6570e88 (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 4ac89f177dac155aea3f5c8c1fdd308f0977cef6
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Thu Jul 9 12:41:11 2015 +0200

    kernel: fix missing rootdev on xen installation.

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

Summary of changes:
 src/paks/linux-pae/install.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Difference in files:
diff --git a/src/paks/linux-pae/install.sh b/src/paks/linux-pae/install.sh
index 27e665f..4ebb38b 100644
--- a/src/paks/linux-pae/install.sh
+++ b/src/paks/linux-pae/install.sh
@@ -45,7 +45,7 @@ function find_partition() {
 extract_files
 #
 KVER=xxxKVERxxx
-
+ROOT=`find_partition /`
 #
 # Create new module depency
 #


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

                 reply	other threads:[~2015-07-09 10:41 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=20150709104151.75A9D2239D@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