From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Re-approaching package tagging
Date: Fri, 21 Dec 2018 22:06:17 +0100 [thread overview]
Message-ID: <87zhsylhdi.fsf@gnu.org> (raw)
In-Reply-To: <87h8f8xy6u.fsf@dustycloud.org> (Christopher Lemmer Webber's message of "Thu, 20 Dec 2018 05:57:45 -0500")
Hi,
Christopher Lemmer Webber <cwebber@dustycloud.org> skribis:
> I wonder for keywords that would be awkward to "force" into the
> description if we could have an "extra keywords" section? Then we can
> skip tagging, but in case a package's description didn't comfortably fit
> that word, you can still find it by it. Then it's not separate tagging,
> just extra words to find a package by that the description didn't say.
Good question. I don’t think we’ve really had concerns about “extra
words” in the past (and the regexps are also matched against the file
name for instance, which can also help), but let’s keep that suggestion
in mind if that happens!
Ludo’.
next prev parent reply other threads:[~2018-12-21 21:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 19:01 Re-approaching package tagging Christopher Lemmer Webber
2018-12-17 20:57 ` swedebugia
2018-12-17 23:08 ` zimoun
2018-12-18 7:48 ` Catonano
2018-12-18 11:34 ` Catonano
2018-12-19 6:51 ` swedebugia
2018-12-19 7:42 ` swedebugia
2018-12-18 11:29 ` Ludovic Courtès
2018-12-18 14:54 ` Christopher Lemmer Webber
2018-12-18 10:36 ` zimoun
2018-12-19 15:04 ` Ludovic Courtès
2018-12-18 20:46 ` zimoun
2018-12-19 23:12 ` zimoun
2018-12-20 7:53 ` Ludovic Courtès
2018-12-20 9:44 ` Chris Marusich
2018-12-21 21:00 ` Ludovic Courtès
2018-12-20 10:57 ` Christopher Lemmer Webber
2018-12-20 11:55 ` swedebugia
2018-12-21 21:06 ` Ludovic Courtès [this message]
2018-12-19 15:05 ` Ludovic Courtès
2018-12-18 20:48 ` zimoun
2018-12-20 7:55 ` Ludovic Courtès
2018-12-20 14:42 ` zimoun
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhsylhdi.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cwebber@dustycloud.org \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).