From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [RFC] common/tags: create file.
Date: Fri, 07 Aug 2020 04:41:52 +0200 [thread overview]
Message-ID: <20200807024152.CkOvp6phqXfDpDpPaAoVbWW8D9VaAtshGfiCF0aifOc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22904@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
There's a closed pull request on the void-packages repository
[RFC] common/tags: create file.
https://github.com/void-linux/void-packages/pull/22904
Description:
Tags taken from relevant "Facets" in
https://packages.debian.org/about/debtags
Fixes (?) #22191
Needs discussion regarding:
- will there be an xlint?
- how many tags are needed?
- what explanations should we have for each tag?
- how would we limit tags to those in the list?
- does the current build infrastructure also deal with tags correctly?
- is this the correct file to create?
- and, of course, should we commit to tags?
parent reply other threads:[~2020-08-07 2:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22904@inbox.vuxu.org>]
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=20200807024152.CkOvp6phqXfDpDpPaAoVbWW8D9VaAtshGfiCF0aifOc@z \
--to=ericonr@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).