public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/smem] epel10: convert GPLv2+ license to SPDX
Date: Tue, 28 Jul 2026 12:34:13 GMT [thread overview]
Message-ID: <178524205390.1.11789631290722921300.rpms-smem-d26fb4b1f0b5@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/smem
Branch : epel10
Commit : d26fb4b1f0b5e2b22f44d6c122fab48e3578a936
Author : Miroslav Suchý <msuchy@redhat.com>
Date : 2024-07-26T02:59:34+02:00
Stats : +2/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/smem/c/d26fb4b1f0b5e2b22f44d6c122fab48e3578a936?branch=epel10
Log:
convert GPLv2+ license to SPDX
This is part of https://fedoraproject.org/wiki/Changes/SPDX_Licenses_Phase_4
---
diff --git a/smem.spec b/smem.spec
index c3e0765..2af0e89 100644
--- a/smem.spec
+++ b/smem.spec
@@ -3,7 +3,8 @@ Version: 1.5
Release: %autorelease
Summary: Report application memory usage in a meaningful way
-License: GPLv2+
+# Automatically converted from old format: GPLv2+ - review is highly recommended.
+License: GPL-2.0-or-later
URL: http://www.selenic.com/smem/
Source0: https://selenic.com/repo/smem/archive/%{version}.tar.gz#/%{name}-%{version}.tar.gz
Patch0: smem-1.5-python3path.patch
reply other threads:[~2026-07-28 12:34 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=178524205390.1.11789631290722921300.rpms-smem-d26fb4b1f0b5@fedoraproject.org \
--to=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