From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 93cad66b4e1c28f9642f64bdc9600d89ec1b9555
Date: Mon, 02 Feb 2015 14:39:01 +0100 [thread overview]
Message-ID: <20150202133901.D716121831@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1668 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 93cad66b4e1c28f9642f64bdc9600d89ec1b9555 (commit)
from db5b0f969331bcc3945b32a4595b8484da1dc8fb (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 93cad66b4e1c28f9642f64bdc9600d89ec1b9555
Author: root <root(a)ipfire.localdomain>
Date: Mon Feb 2 14:38:16 2015 +0100
core87: serial console update part 2.
-----------------------------------------------------------------------
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 5a7b59a..ab72e68 100644
--- a/config/rootfiles/core/86/update.sh
+++ b/config/rootfiles/core/86/update.sh
@@ -172,7 +172,7 @@ case "$(uname -m)" in
echo Update grub configuration ...
if grep -qE "^serial" /boot/old-grub-config; then
sed -i /etc/default/grub \
- -e "s| panic=10 | console=ttyS0,115200n8 panic=10 |g"
+ -e "s|panic=10|& console=ttyS0,115200n8|g"
echo "GRUB_TERMINAL=\"serial\"" >> /etc/default/grub
echo "GRUB_SERIAL_COMMAND=\"serial --unit=0 --speed=115200\"" >> /etc/default/grub
fi
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-02-02 13: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=20150202133901.D716121831@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