From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 1cab447f8fbf0aa35af9d65a1c44885a5dd12eec
Date: Sun, 13 Jan 2013 22:29:16 +0100 [thread overview]
Message-ID: <20130113212916.AF5D6200AB@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1616 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 1cab447f8fbf0aa35af9d65a1c44885a5dd12eec (commit)
from 940da289efa4379002e129f40ab78bc0ded465fd (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 1cab447f8fbf0aa35af9d65a1c44885a5dd12eec
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Jan 13 22:27:25 2013 +0100
updater: add xvc0 to /etc/securetty on xen update.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/66/update.sh | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/66/update.sh b/config/rootfiles/core/66/update.sh
index 750f8aa..4a3f38d 100644
--- a/config/rootfiles/core/66/update.sh
+++ b/config/rootfiles/core/66/update.sh
@@ -330,6 +330,8 @@ if [ -e "/opt/pakfire/db/installed/meta-linux-xen" ]; then
echo "Name: linux-xen" > /opt/pakfire/db/installed/meta-linux-xen
echo "ProgVersion: 2.6.32.60" >> /opt/pakfire/db/installed/meta-linux-xen
echo "Release: 23" >> /opt/pakfire/db/installed/meta-linux-xen
+ # Add xvc0 to /etc/securetty
+ echo "xvc0" >> /etc/securetty
fi
#
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-01-13 21:29 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=20130113212916.AF5D6200AB@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