public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/python-uv-build] f43: Comment typo fix in .rpmlintrc file
Date: Thu, 19 Nov 2026 20:31:19 GMT	[thread overview]
Message-ID: <179512027953.1.9929140422602382774.rpms-python-uv-build-acd9bf7cccf0@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-uv-build
            Branch : f43
            Commit : acd9bf7cccf07d3765d13545f0636575c9aa0005
            Author : Benjamin A. Beasley <code@musicinmybrain.net>
            Date   : 2026-11-05T07:39:20+00:00
            Stats  : +2/-2 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-uv-build/c/acd9bf7cccf07d3765d13545f0636575c9aa0005?branch=f43

            Log:
            Comment typo fix in .rpmlintrc file

[skip changelog]

---
diff --git a/python-uv-build.rpmlintrc b/python-uv-build.rpmlintrc
index f2a1050..35c4187 100644
--- a/python-uv-build.rpmlintrc
+++ b/python-uv-build.rpmlintrc
@@ -3,6 +3,6 @@
 #   on the CLI. Use `uv build` or another build frontend instead.
 # Therefore, it does not make sense to package a man page.
 addFilter(r" no-manual-page-for-binary uv-build$")
-# Some licenses in LICENSE.bundled have the same text. It is not straighforward
-# to hardlink them, and the amount of wasted space is small.
+# Some licenses in LICENSE.bundled have the same text. It is not
+# straightforward to hardlink them, and the amount of wasted space is small.
 addFilter(r" files-duplicate( \S+/LICENSE\.bundled/\S+)+$")

                 reply	other threads:[~2026-11-19 20:31 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=179512027953.1.9929140422602382774.rpms-python-uv-build-acd9bf7cccf0@fedoraproject.org \
    --to=code@musicinmybrain.net \
    --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