From: Mike Gerwitz <mtg@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>, 33844@debbugs.gnu.org
Subject: bug#33844: Rename ghc-pandoc to pandoc
Date: Fri, 28 Feb 2020 00:03:06 -0500 [thread overview]
Message-ID: <87wo87e22d.fsf__18920.8696059481$1582866310$gmane$org@gnu.org> (raw)
In-Reply-To: <CAJ3okZ2-Mz=Bh6dbg7BEcH54Vc0RMRDfCOkqTJzP=cW4S2wAJg@mail.gmail.com> (zimoun's message of "Thu, 27 Feb 2020 14:10:15 +0100")
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
On Thu, Feb 27, 2020 at 14:10:15 +0100, zimoun wrote:
> Well, your comment is pointing: a) that the description is badly
> written and b) the 'relevance' score is too rough.
[...]
> The real problem is not the non-obvious name (ghc-pandoc instead of
> simply pandoc) but it is: a) some descriptions are badly written and
> b) the 'relevance' scoring function is not enough "smart" to detect
> them.
Thank you for taking the time to explain this.
--
Mike Gerwitz
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2020-02-28 5:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 8:46 bug#33844: Rename ghc-pandoc to pandoc swedebugia
2020-02-26 10:06 ` Pierre Neidhardt
[not found] ` <878skpacih.fsf@ambrevar.xyz>
2020-02-26 10:23 ` Efraim Flashner
2020-02-26 10:23 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-02-26 11:57 ` Ricardo Wurmus
[not found] ` <87wo89imsx.fsf@elephly.net>
2020-02-26 12:17 ` Pierre Neidhardt
[not found] ` <87wo898rv3.fsf@ambrevar.xyz>
2020-02-26 12:52 ` Pierre Neidhardt
2020-09-09 16:08 ` zimoun
2020-09-09 16:11 ` Ricardo Wurmus
2020-10-07 15:27 ` zimoun
2020-12-19 0:03 ` zimoun
[not found] ` <20200226102314.GE12956@E5400>
2020-02-27 1:23 ` Mike Gerwitz
[not found] ` <87pne0q0wb.fsf@gnu.org>
2020-02-27 13:10 ` zimoun
[not found] ` <CAJ3okZ2-Mz=Bh6dbg7BEcH54Vc0RMRDfCOkqTJzP=cW4S2wAJg@mail.gmail.com>
2020-02-28 5:03 ` Mike Gerwitz [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
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='87wo87e22d.fsf__18920.8696059481$1582866310$gmane$org@gnu.org' \
--to=mtg@gnu.org \
--cc=33844@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).