From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 829b0ba85156fbf3514b3f5d5b13c0f3254fae49
Date: Thu, 18 Feb 2016 05:30:12 +0000 [thread overview]
Message-ID: <20160218053013.1A2D21081BC7@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1585 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 829b0ba85156fbf3514b3f5d5b13c0f3254fae49 (commit)
from 8c065b268d8c04c48e76dde8109381823a601908 (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 829b0ba85156fbf3514b3f5d5b13c0f3254fae49
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Feb 18 04:31:28 2016 +0100
core98: fix typo
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/98/update.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/98/update.sh b/config/rootfiles/core/98/update.sh
index 89d3245..7e0cc2d 100644
--- a/config/rootfiles/core/98/update.sh
+++ b/config/rootfiles/core/98/update.sh
@@ -40,7 +40,7 @@ extract_files
if [ -e /boot/grub/grub.conf ]; then
# legacy grub config on xen or citrix conflicts with grub2 config
# and core96 contains an empty file
- if [ ! -s /boot/grub/grub.cfg ]
+ if [ ! -s /boot/grub/grub.cfg ]; then
rm /boot/grub/grub.cfg
fi
fi
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-02-18 5:30 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=20160218053013.1A2D21081BC7@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