From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core73, updated. 303b81f19c37636402d2e5f850cb683e051bbe10
Date: Sun, 24 Nov 2013 00:49:29 +0100 [thread overview]
Message-ID: <20131123234930.098EA2153E@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1648 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, core73 has been updated
via 303b81f19c37636402d2e5f850cb683e051bbe10 (commit)
from d48c456fa24545b6d9b06049fcef57850f1e02dc (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 -----------------------------------------------------------------
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/36 => core/73}/filelists/openssh | 0
config/rootfiles/core/73/update.sh | 2 +-
2 files changed, 1 insertion(+), 1 deletion(-)
copy config/rootfiles/{oldcore/36 => core/73}/filelists/openssh (100%)
Difference in files:
diff --git a/config/rootfiles/core/73/filelists/openssh b/config/rootfiles/core/73/filelists/openssh
new file mode 120000
index 0000000..d8c77fd
--- /dev/null
+++ b/config/rootfiles/core/73/filelists/openssh
@@ -0,0 +1 @@
+../../../common/openssh
\ No newline at end of file
diff --git a/config/rootfiles/core/73/update.sh b/config/rootfiles/core/73/update.sh
index ee799ad..a9fed1b 100644
--- a/config/rootfiles/core/73/update.sh
+++ b/config/rootfiles/core/73/update.sh
@@ -70,7 +70,7 @@ fi
sync
# This update need a reboot...
-#touch /var/run/need_reboot
+touch /var/run/need_reboot
#
#Finish
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-11-23 23:49 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=20131123234930.098EA2153E@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