From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 3bee566f45d2a3789b80a1b9fab01f21a635987d
Date: Thu, 17 Aug 2017 13:20:50 +0100 [thread overview]
Message-ID: <20170817122050.BE2ED1081DE1@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1531 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 3bee566f45d2a3789b80a1b9fab01f21a635987d (commit)
from 16388774a4c8dc428722b762da590cf7e070241e (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 3bee566f45d2a3789b80a1b9fab01f21a635987d
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Aug 17 13:14:53 2017 +0100
core113: Ship openvpn which has been missing in core112 updater
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/100 => core/113}/filelists/openvpn | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/100 => core/113}/filelists/openvpn (100%)
Difference in files:
diff --git a/config/rootfiles/core/113/filelists/openvpn b/config/rootfiles/core/113/filelists/openvpn
new file mode 120000
index 0000000..493f3f7
--- /dev/null
+++ b/config/rootfiles/core/113/filelists/openvpn
@@ -0,0 +1 @@
+../../../common/openvpn
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-08-17 12:20 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=20170817122050.BE2ED1081DE1@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