From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: New Package: tldr-0.6.1
Date: Wed, 01 Jan 2020 18:36:30 +0100 [thread overview]
Message-ID: <20200101173630.v-sDaVG3tFWZnED6QROgB3EE0ffcrW3KtJPXtkAPfuk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17912@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/17912#issuecomment-570070095
Comment:
I'd just call the binary tealdeer, because that's the project name anyway. Can you do this? I can't push to this branch, and they should be merged together.
Just one note, I'm not convinced that gtldr is a good name, because there are more tldr tools written in go. tldrpp, tldr-plus-plus or something like that would be based on the actual project name and would therefore be a better fit. I'm not in a position to decide this obviously, but that's just my opinion here :D
next prev parent reply other threads:[~2020-01-01 17:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 0:32 [PR PATCH] " voidlinux-github
2019-12-31 2:55 ` voidlinux-github
2019-12-31 2:57 ` voidlinux-github
2019-12-31 3:07 ` [PR PATCH] [Updated] " voidlinux-github
2019-12-31 3:08 ` voidlinux-github
2019-12-31 3:20 ` voidlinux-github
2019-12-31 3:21 ` [PR PATCH] [Closed]: " voidlinux-github
2019-12-31 3:21 ` voidlinux-github
2019-12-31 3:29 ` voidlinux-github
2019-12-31 3:31 ` [PR PATCH] [Updated] " voidlinux-github
2019-12-31 9:34 ` voidlinux-github
2019-12-31 9:36 ` voidlinux-github
2019-12-31 9:38 ` voidlinux-github
2019-12-31 12:01 ` voidlinux-github
2019-12-31 14:07 ` voidlinux-github
2019-12-31 15:33 ` voidlinux-github
2019-12-31 15:38 ` voidlinux-github
2020-01-01 1:18 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-01 1:24 ` voidlinux-github
2020-01-01 16:54 ` voidlinux-github
2020-01-01 17:12 ` voidlinux-github
2020-01-01 17:36 ` voidlinux-github [this message]
2020-01-01 17:37 ` voidlinux-github
2020-01-01 19:47 ` voidlinux-github
2020-01-01 21:28 ` voidlinux-github
2020-01-01 21:55 ` voidlinux-github
2020-01-02 0:04 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-02 0:44 ` voidlinux-github
2020-01-02 15:07 ` voidlinux-github
2020-01-03 13:20 ` voidlinux-github
2020-01-03 13:24 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-17 18:24 ` [PR PATCH] [Merged]: " voidlinux-github
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=20200101173630.v-sDaVG3tFWZnED6QROgB3EE0ffcrW3KtJPXtkAPfuk@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).