From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] vim: Update to version 9.1.2147
Date: Sat, 14 Feb 2026 16:20:40 +0100 [thread overview]
Message-ID: <20260214152040.3720549-20-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20260214152040.3720549-1-adolf.belka@ipfire.org>
- Update from version 9.1.2098 to 9.1.2147
- Update of rootfile
- Changelog is not available. Generally each patch version number update is related to
a commit entry in the git repository. The details for all the commit changes can be
found at https://github.com/vim/vim/commits/master/
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
config/rootfiles/common/vim | 11 +++++++++++
lfs/vim | 4 ++--
2 files changed, 13 insertions(+), 2 deletions(-)
diff --git a/config/rootfiles/common/vim b/config/rootfiles/common/vim
index 3551f84d0..8352c865e 100644
--- a/config/rootfiles/common/vim
+++ b/config/rootfiles/common/vim
@@ -115,6 +115,7 @@ usr/share/vim
#usr/share/vim/vim91/colors
#usr/share/vim/vim91/colors/README.txt
#usr/share/vim/vim91/colors/blue.vim
+#usr/share/vim/vim91/colors/catppuccin.vim
#usr/share/vim/vim91/colors/darkblue.vim
#usr/share/vim/vim91/colors/default.vim
#usr/share/vim/vim91/colors/delek.vim
@@ -629,6 +630,7 @@ usr/share/vim
#usr/share/vim/vim91/ftplugin/kconfig.vim
#usr/share/vim/vim91/ftplugin/kdl.vim
#usr/share/vim/vim91/ftplugin/kerml.vim
+#usr/share/vim/vim91/ftplugin/kitty.vim
#usr/share/vim/vim91/ftplugin/kivy.vim
#usr/share/vim/vim91/ftplugin/kotlin.vim
#usr/share/vim/vim91/ftplugin/kwt.vim
@@ -783,6 +785,7 @@ usr/share/vim
#usr/share/vim/vim91/ftplugin/sh.vim
#usr/share/vim/vim91/ftplugin/shaderslang.vim
#usr/share/vim/vim91/ftplugin/sieve.vim
+#usr/share/vim/vim91/ftplugin/skhd.vim
#usr/share/vim/vim91/ftplugin/slint.vim
#usr/share/vim/vim91/ftplugin/slpconf.vim
#usr/share/vim/vim91/ftplugin/slpreg.vim
@@ -1869,6 +1872,7 @@ usr/share/vim
#usr/share/vim/vim91/syntax/sindacmp.vim
#usr/share/vim/vim91/syntax/sindaout.vim
#usr/share/vim/vim91/syntax/sisu.vim
+#usr/share/vim/vim91/syntax/skhd.vim
#usr/share/vim/vim91/syntax/skill.vim
#usr/share/vim/vim91/syntax/sl.vim
#usr/share/vim/vim91/syntax/slang.vim
@@ -2075,6 +2079,7 @@ usr/share/vim
#usr/share/vim/vim91/tutor
#usr/share/vim/vim91/tutor/README.el.txt
#usr/share/vim/vim91/tutor/README.ru.txt
+#usr/share/vim/vim91/tutor/README.sv.txt
#usr/share/vim/vim91/tutor/README.txt
#usr/share/vim/vim91/tutor/en
#usr/share/vim/vim91/tutor/en/vim-01-beginner.tutor
@@ -2094,6 +2099,11 @@ usr/share/vim
#usr/share/vim/vim91/tutor/sr/vim-01-beginner.tutor.json
#usr/share/vim/vim91/tutor/sr/vim-02-beginner.tutor
#usr/share/vim/vim91/tutor/sr/vim-02-beginner.tutor.json
+#usr/share/vim/vim91/tutor/sv
+#usr/share/vim/vim91/tutor/sv/vim-01-beginner.tutor
+#usr/share/vim/vim91/tutor/sv/vim-01-beginner.tutor.json
+#usr/share/vim/vim91/tutor/sv/vim-02-beginner.tutor
+#usr/share/vim/vim91/tutor/sv/vim-02-beginner.tutor.json
#usr/share/vim/vim91/tutor/tutor.tutor
#usr/share/vim/vim91/tutor/tutor.tutor.json
#usr/share/vim/vim91/tutor/tutor.vim
@@ -2138,4 +2148,5 @@ usr/share/vim
#usr/share/vim/vim91/tutor/tutor2.ja
#usr/share/vim/vim91/tutor/tutor2.ru
#usr/share/vim/vim91/tutor/tutor2.sr
+#usr/share/vim/vim91/tutor/tutor2.sv
#usr/share/vim/vim91/vimrc_example.vim
diff --git a/lfs/vim b/lfs/vim
index 77bf5148e..9052858ec 100644
--- a/lfs/vim
+++ b/lfs/vim
@@ -24,7 +24,7 @@
include Config
-VER = 9.1.2098
+VER = 9.1.2147
THISAPP = vim-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -44,7 +44,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 3d852d79416672decee3b9e46b27ff5f5ece77410028da96814a20525b984d6c2a9ae356e2449da521310a033709fb05da237d2269ddad2f1843f953b8c2891a
+$(DL_FILE)_BLAKE2 = 1f697c77175faf75c7587426684f88e44ab7ac8eee8ca73b74e95303e01be842b8129596928389122011063b9a1e402b83efc904bff350c1eaab7b3d6b851461
install : $(TARGET)
--
2.53.0
prev parent reply other threads:[~2026-02-14 15:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 15:20 [PATCH] core201: Ship hwdata Adolf Belka
2026-02-14 15:20 ` [PATCH] core201: Ship intel-microcode Adolf Belka
2026-02-14 15:20 ` [PATCH] core201: Ship libgcrypt Adolf Belka
2026-02-14 15:20 ` [PATCH] core201: Ship libpng Adolf Belka
2026-02-14 15:20 ` [PATCH] core201: Ship libuv Adolf Belka
2026-02-14 15:20 ` [PATCH] core201: Ship openvpn Adolf Belka
2026-02-14 15:20 ` [PATCH] core201: Ship vim Adolf Belka
2026-02-14 15:20 ` [PATCH] git: Update to version 2.53.0 Adolf Belka
2026-02-14 15:20 ` [PATCH] hwdata: Update to version 0.404 Adolf Belka
2026-02-14 15:20 ` [PATCH] intel-microcode: Update to version 20260210 Adolf Belka
2026-02-14 15:20 ` [PATCH] less: Update to version 692 Adolf Belka
2026-02-14 15:20 ` [PATCH] libgcrypt: Update to version 1.12.0 Adolf Belka
2026-02-14 15:20 ` [PATCH] libpng: Update to version 1.6.55 Adolf Belka
2026-02-14 15:20 ` [PATCH] libtalloc: Update to version 2.4.4 Adolf Belka
2026-02-14 15:20 ` [PATCH] libuv: Update to version 1.52.0 Adolf Belka
2026-02-14 15:20 ` [PATCH] nfs: Update to version 2.8.5 Adolf Belka
2026-02-14 15:20 ` [PATCH] openvpn: Update to version 2.6.19 Adolf Belka
2026-02-14 15:20 ` [PATCH] p11-kit: Update to version 0.26.2 Adolf Belka
2026-02-14 15:20 ` [PATCH] postfix: Update to version 3.10.7 Adolf Belka
2026-02-14 15:20 ` Adolf Belka [this message]
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=20260214152040.3720549-20-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@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