From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. b46967b0d337971d72dd66a660abc5cf30836f04
Date: Thu, 14 Sep 2023 12:07:12 +0000 [thread overview]
Message-ID: <4RmbfS2W41z2xlv@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1456 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 3.x development tree".
The branch, master has been updated
via b46967b0d337971d72dd66a660abc5cf30836f04 (commit)
from 13096b8e18efc7558621cbc3d3ab5cb1a666cda2 (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 b46967b0d337971d72dd66a660abc5cf30836f04
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Sep 14 12:06:39 2023 +0000
vim: Rebuild against new glibc
VIM immediately crashes and rebuilding it fixes the problem.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
vim/vim.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/vim/vim.nm b/vim/vim.nm
index 7efb260e0..5e056c4ba 100644
--- a/vim/vim.nm
+++ b/vim/vim.nm
@@ -8,7 +8,7 @@ major_ver = 8
minor_ver = 0
patchlevel = 1184
version = %{major_ver}.%{minor_ver}.%{patchlevel}
-release = 2
+release = 2.1
groups = Applications/Editors
url = http://www.vim.org
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2023-09-14 12:07 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=4RmbfS2W41z2xlv@people01.haj.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