From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 8e101c0bdaea04dc759773342d719b8daeb95f67
Date: Mon, 10 Jun 2019 19:45:17 +0100 [thread overview]
Message-ID: <20190610184517.7CFE984FDBF@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1710 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 8e101c0bdaea04dc759773342d719b8daeb95f67 (commit)
from 35f12f29983b0baa0df6736b10f02b6e78c85030 (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 8e101c0bdaea04dc759773342d719b8daeb95f67
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Mon Jun 10 18:22:00 2019 +0000
ship language files in Core Update 133
These were missing in Core Update 132, and some strings
(especially on the "CPU vulnerabilities" page) missed translations.
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/133/filelists/files | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/133/filelists/files b/config/rootfiles/core/133/filelists/files
index 7998df231..212211dd7 100644
--- a/config/rootfiles/core/133/filelists/files
+++ b/config/rootfiles/core/133/filelists/files
@@ -11,3 +11,4 @@ usr/local/bin/update-ids-ruleset
usr/sbin/convert-ids-modifysids-file
usr/sbin/convert-snort
var/ipfire/ids-functions.pl
+var/ipfire/langs
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-06-10 18:45 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=20190610184517.7CFE984FDBF@people01.i.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