From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. cb679b1eb965e0df188b50ab0337cf1687ed70cb
Date: Tue, 08 Mar 2016 21:13:34 +0000 [thread overview]
Message-ID: <20160308211334.952581081BC7@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1503 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 cb679b1eb965e0df188b50ab0337cf1687ed70cb (commit)
from 03022f412ef2d4cfd0bad133988f2cc3312728d1 (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 cb679b1eb965e0df188b50ab0337cf1687ed70cb
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Mar 8 21:32:29 2016 +0100
core100: add missing openssl rootfile to updater
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/97 => core/100}/filelists/openssl | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/97 => core/100}/filelists/openssl (100%)
Difference in files:
diff --git a/config/rootfiles/core/100/filelists/openssl b/config/rootfiles/core/100/filelists/openssl
new file mode 120000
index 0000000..e011a92
--- /dev/null
+++ b/config/rootfiles/core/100/filelists/openssl
@@ -0,0 +1 @@
+../../../common/openssl
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-03-08 21:13 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=20160308211334.952581081BC7@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