From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Tag KDE Gear as 'kde-gear'
Date: Sat, 26 Feb 2022 21:12:44 +0100 [thread overview]
Message-ID: <20220226201244.CI91TJba1nsAJay2HB9vIcK6m3CmbXLE4T7xk49fuUI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35808@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1826 bytes --]
There's a closed pull request on the void-packages repository
Tag KDE Gear as 'kde-gear'
https://github.com/void-linux/void-packages/pull/35808
Description:
[ci skip]
I'm not sure if this is everyone's interest but I thought it would be convenient to have KDE Gear tagged as what it is.
I am aware that tags are currently not used but I'd like to introduce them for some obvious cases where it can help users find software, in this case software that belongs to KDE.
It also helps us keeping track of updates because they all should have the same version.
I got the list from: https://invent.kde.org/sysadmin/release-tools/-/blob/release/21.12/modules.git
Before we merge this it would be good to have `tags` listed in xlint to make it's place standardized. Maybe around `short_desc` is a good place? Let me know what you think :)
EDIT: Well, I'm gonna mark this as a draft as long #22191 is not resolved.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2022-02-26 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 19:58 [PR PATCH] " tibequadorian
2022-02-23 20:00 ` [PR PATCH] [Updated] " tibequadorian
2022-02-23 20:04 ` tibequadorian
2022-02-23 20:15 ` tibequadorian
2022-02-23 22:30 ` Johnnynator
2022-02-26 20:12 ` tibequadorian [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=20220226201244.CI91TJba1nsAJay2HB9vIcK6m3CmbXLE4T7xk49fuUI@z \
--to=tibequadorian@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).