public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Gwyn Ciesla <gwync@protonmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/cppcheck] f44: 2.21.1
Date: Mon, 22 Jun 2026 15:56:36 GMT [thread overview]
Message-ID: <178214379672.1.6300839834440256422.rpms-cppcheck-bebd627c04d7@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/cppcheck
Branch : f44
Commit : bebd627c04d7a46f0b4dbffe98ed35d77fa21092
Author : Gwyn Ciesla <gwync@protonmail.com>
Date : 2026-06-22T10:54:13-05:00
Stats : +6/-2 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/cppcheck/c/bebd627c04d7a46f0b4dbffe98ed35d77fa21092?branch=f44
Log:
2.21.1
---
diff --git a/.gitignore b/.gitignore
index 55f0f3e..45a71a8 100644
--- a/.gitignore
+++ b/.gitignore
@@ -73,3 +73,4 @@ cppcheck-1.44.tar.bz2
/cppcheck-2.20.0.tar.gz
/cppcheck-2.20.1.tar.gz
/cppcheck-2.21.0.tar.gz
+/cppcheck-2.21.1.tar.gz
diff --git a/cppcheck.spec b/cppcheck.spec
index f564787..fa02b28 100644
--- a/cppcheck.spec
+++ b/cppcheck.spec
@@ -5,7 +5,7 @@
%endif
Name: cppcheck
-Version: 2.21.0
+Version: 2.21.1
Release: 1%{?dist}
Summary: Tool for static C/C++ code analysis
License: GPL-3.0-or-later
@@ -137,6 +137,9 @@ grep -l "#\!/usr/bin/env python3" %{buildroot}%{_datadir}/Cppcheck/addons/*.py |
%{_bindir}/cppcheck-htmlreport
%changelog
+* Mon Jun 22 2026 Gwyn Ciesla <gwync@protonmail.com> - 2.21.1-1
+- 2.21.1
+
* Thu Jun 04 2026 Gwyn Ciesla <gwync@protonmail.com> - 2.21.0-1
- 2.21.0
diff --git a/sources b/sources
index d021d99..abb1b18 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (cppcheck-2.21.0.tar.gz) = 0e08c72975243569985e9098519d7cca8e84a8687a496e406234e1be1f3e71c039e4d21437d00866244bd0a8a60dd30fc70756125bf0347ce3b2d809b0a9b4f9
+SHA512 (cppcheck-2.21.1.tar.gz) = f07814cfe9c0430ce605ef39c552e0889fcba0a4a38244170615888a5ae8cbf5f0709332ef6154b6350ad9e08fd3fce7d82e21c38aaeb916545577b06672016f
reply other threads:[~2026-06-22 15:56 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=178214379672.1.6300839834440256422.rpms-cppcheck-bebd627c04d7@fedoraproject.org \
--to=gwync@protonmail.com \
--cc=git-commits@fedoraproject.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