From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core133, updated. f2bdc3a4a09b5fc03a902c830ccc1fd7653b9f10
Date: Wed, 26 Jun 2019 21:30:13 +0100 [thread overview]
Message-ID: <20190626203013.7D5F480F69C@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1720 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, core133 has been updated
via f2bdc3a4a09b5fc03a902c830ccc1fd7653b9f10 (commit)
from 460b6b40018b2900229b51396ab7ef92cf75768c (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 f2bdc3a4a09b5fc03a902c830ccc1fd7653b9f10
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Jun 26 22:29:55 2019 +0200
Revert "linux: Fix rootfile to ship GeoIP modules"
This reverts commit 460b6b40018b2900229b51396ab7ef92cf75768c.
-----------------------------------------------------------------------
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 6929adc0e..49937b655 100644
--- a/config/rootfiles/common/x86_64/linux
+++ b/config/rootfiles/common/x86_64/linux
@@ -18480,7 +18480,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-26 20:30 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=20190626203013.7D5F480F69C@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