Github messages for voidlinux
 help / color / mirror / Atom feed
From: zdykstra <zdykstra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: fuzzypkg-1.0.2
Date: Sat, 10 Oct 2020 07:22:46 +0200	[thread overview]
Message-ID: <20201010052246.t-dayIYV342t8R1zV0QLohstvR1j13Qgw7zcoVszOjQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25481@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 653 bytes --]

New review comment by zdykstra on void-packages repository

https://github.com/void-linux/void-packages/pull/25481#discussion_r502748720

Comment:
I'm not trying to be difficult here. I just haven't seen a reasonable technical argument against changing run-time depends based on availability. 

It's obviously not an issue to have both `skim` and `fzf` installed - upstream (in this case, me) prefers the usage of `fzf` where possible. Since you're now putting me in the position of having to meet someones definition of *something really important*, I don't know what else to say. I simply wanted to contribute a tool that I thought would be useful.

  parent reply	other threads:[~2020-10-10  5:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 22:16 [PR PATCH] New package: fuzzypkg-1.0.0 zdykstra
2020-10-09 22:31 ` [PR REVIEW] " ericonr
2020-10-10  0:46 ` q66
2020-10-10  1:07 ` zdykstra
2020-10-10  1:17 ` q66
2020-10-10  2:34 ` [PR PATCH] [Updated] " zdykstra
2020-10-10  3:32 ` [PR REVIEW] New package: fuzzypkg-1.0.1 q66
2020-10-10  3:48 ` zdykstra
2020-10-10  3:52 ` q66
2020-10-10  4:45 ` [PR PATCH] [Updated] " zdykstra
2020-10-10  5:22 ` zdykstra [this message]
2020-10-10 14:45 ` [PR REVIEW] New package: fuzzypkg-1.0.2 q66
2020-11-22  3:27 ` [PR PATCH] [Merged]: " the-maldridge

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=20201010052246.t-dayIYV342t8R1zV0QLohstvR1j13Qgw7zcoVszOjQ@z \
    --to=zdykstra@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).