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, master, updated. 75f3abe29d048b3e4096c28ef1ce32121fe69795
Date: Mon, 22 Dec 2014 20:52:20 +0100	[thread overview]
Message-ID: <20141222195220.727AB219A9@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1509 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, master has been updated
       via  75f3abe29d048b3e4096c28ef1ce32121fe69795 (commit)
      from  81f315bff2e161073c12733a01a635b22e97f89f (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 75f3abe29d048b3e4096c28ef1ce32121fe69795
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Mon Dec 22 20:51:42 2014 +0100

    core86: fix init restart.

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

Summary of changes:
 config/rootfiles/core/86/update.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Difference in files:
diff --git a/config/rootfiles/core/86/update.sh b/config/rootfiles/core/86/update.sh
index db38844..bdb96fc 100644
--- a/config/rootfiles/core/86/update.sh
+++ b/config/rootfiles/core/86/update.sh
@@ -128,7 +128,7 @@ tar xavf /opt/pakfire/tmp/files* --no-overwrite-dir -p --numeric-owner -C /
 
 #
 #restart init because glibc was updated.
-telinit i
+telinit u
 
 # Check diskspace on boot
 BOOTSPACE=`df /boot -Pk | sed "s| * | |g" | cut -d" " -f4 | tail -n 1`


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

                 reply	other threads:[~2014-12-22 19:52 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=20141222195220.727AB219A9@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