Github messages for voidlinux
 help / color / mirror / Atom feed
From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] python3-crccheck: update to 1.1
Date: Thu, 23 Dec 2021 04:16:23 +0100	[thread overview]
Message-ID: <20211223031623.sxFGCxeLtIvOarYc4HFEsloCq32xDKzTDx7PlcLnGfw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34672@inbox.vuxu.org>

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

New review comment by abenson on void-packages repository

https://github.com/void-linux/void-packages/pull/34672#discussion_r774291975

Comment:
`checkdepends="${depends} python3-pytest python3-nose"`

  reply	other threads:[~2021-12-23  3:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23  3:12 [PR PATCH] " misuchiru03
2021-12-23  3:16 ` abenson [this message]
2021-12-23  3:34 ` [PR PATCH] [Updated] " misuchiru03
2021-12-23  3:40 ` [PR PATCH] [Merged]: " abenson

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=20211223031623.sxFGCxeLtIvOarYc4HFEsloCq32xDKzTDx7PlcLnGfw@z \
    --to=abenson@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).