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, fifteen, updated. 1a78fe5e2dd19a6c7959ec52e175ee7a70cc29e8
Date: Sat, 14 Sep 2013 12:39:12 +0200	[thread overview]
Message-ID: <20130914103912.2D7AD20F93@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1548 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, fifteen has been updated
       via  1a78fe5e2dd19a6c7959ec52e175ee7a70cc29e8 (commit)
      from  4fa404af2a60ab9faf760e087f9d267f7707dae3 (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 1a78fe5e2dd19a6c7959ec52e175ee7a70cc29e8
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sat Sep 14 12:38:39 2013 +0200

    firstsetup: add missing "fi".

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

Summary of changes:
 src/initscripts/init.d/firstsetup | 1 +
 1 file changed, 1 insertion(+)

Difference in files:
diff --git a/src/initscripts/init.d/firstsetup b/src/initscripts/init.d/firstsetup
index 29de499..247d69a 100644
--- a/src/initscripts/init.d/firstsetup
+++ b/src/initscripts/init.d/firstsetup
@@ -40,6 +40,7 @@ if [ ! "$(grep "^flags.* pae " /proc/cpuinfo)" == "" ]; then
 		echo "Name: linux-pae" > /opt/pakfire/db/installed/meta-linux-pae
 		echo "ProgVersion: 0" >> /opt/pakfire/db/installed/meta-linux-pae
 		echo "Release: 0"     >> /opt/pakfire/db/installed/meta-linux-pae
+	fi
 fi
 
 echo Restarting udev...


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

                 reply	other threads:[~2013-09-14 10:39 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=20130914103912.2D7AD20F93@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