From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core134, updated. 54577393cf2b4f5a54e38567b7553bfa997d1b11
Date: Tue, 25 Jun 2019 11:06:32 +0100 [thread overview]
Message-ID: <20190625100632.EDA1584FDAF@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1714 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, core134 has been updated
via 54577393cf2b4f5a54e38567b7553bfa997d1b11 (commit)
from 4e69701332f4cee583752ed3ff3e4d44b129931d (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 54577393cf2b4f5a54e38567b7553bfa997d1b11
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Jun 24 14:39:30 2019 +0100
linux: Fix rootfile to ship GeoIP modules
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/x86_64/linux | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/common/x86_64/linux b/config/rootfiles/common/x86_64/linux
index 238134dd3..755d7627a 100644
--- a/config/rootfiles/common/x86_64/linux
+++ b/config/rootfiles/common/x86_64/linux
@@ -18484,7 +18484,7 @@ etc/modprobe.d/ipv6.conf
#lib/modules/KVER-ipfire/build/virt/lib
#lib/modules/KVER-ipfire/build/virt/lib/Kconfig
#lib/modules/KVER-ipfire/build/virt/lib/Makefile
-#lib/modules/KVER-ipfire/extra
+lib/modules/KVER-ipfire/extra
lib/modules/KVER-ipfire/kernel
#lib/modules/KVER-ipfire/kernel/arch
#lib/modules/KVER-ipfire/kernel/arch/x86
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-06-25 10:06 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=20190625100632.EDA1584FDAF@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