Github messages for voidlinux
 help / color / mirror / Atom feed
From: ScrelliCopter <ScrelliCopter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: genie-1141
Date: Mon, 18 Jan 2021 16:57:03 +0100	[thread overview]
Message-ID: <20210118155703.Tj4G0y9Nhe17vKF7cM9DENlz8cnZcEbhjvrT9de8Tao@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27915@inbox.vuxu.org>

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

New review comment by ScrelliCopter on void-packages repository

https://github.com/void-linux/void-packages/pull/27915#discussion_r559662958

Comment:
I did mention it in my PR comment, it should be more obvious now from the template (the git requirement is gone anyway).
Rewriting the whole script would be absurd when the issue can be fixed with patches & sed, so I've just opted for that.

  parent reply	other threads:[~2021-01-18 15:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14  8:56 [PR PATCH] " ScrelliCopter
2021-01-14 13:13 ` [PR PATCH] [Updated] " ScrelliCopter
2021-01-14 13:15 ` ScrelliCopter
2021-01-17  0:23 ` [PR REVIEW] " Piraty
2021-01-17  5:18 ` [PR PATCH] [Updated] " ScrelliCopter
2021-01-17  5:32 ` [PR REVIEW] " ScrelliCopter
2021-01-18 12:03 ` Piraty
2021-01-18 12:05 ` Piraty
2021-01-18 15:50 ` [PR PATCH] [Updated] " ScrelliCopter
2021-01-18 15:57 ` ScrelliCopter [this message]
2021-01-18 15:57 ` [PR REVIEW] " ScrelliCopter
2021-01-18 17:48 ` Chocimier
2021-01-19  6:55 ` ScrelliCopter
2021-01-27 14:14 ` [PR REVIEW] " Piraty
2021-01-28  5:57 ` [PR PATCH] [Updated] " ScrelliCopter
2021-01-28  5:59 ` [PR REVIEW] " ScrelliCopter
2021-01-28 14:13 ` Piraty
2021-01-28 14:13 ` Piraty
2021-01-28 20:59 ` [PR PATCH] [Updated] " ScrelliCopter
2021-01-28 21:01 ` [PR REVIEW] " ScrelliCopter
2021-01-28 21:02 ` ScrelliCopter
2021-01-28 21:10 ` ScrelliCopter
2021-01-28 21:11 ` ScrelliCopter
2021-04-26  3:45 ` [PR PATCH] [Closed]: " ScrelliCopter

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=20210118155703.Tj4G0y9Nhe17vKF7cM9DENlz8cnZcEbhjvrT9de8Tao@z \
    --to=screllicopter@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).