Github messages for voidlinux
 help / color / mirror / Atom feed
From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New packages: highway, libjxl, qt-jpegxl-image-plugin
Date: Wed, 27 Apr 2022 20:17:52 +0200	[thread overview]
Message-ID: <20220427181752.3iH4ME2lSp3qZnzhVNHEx9MtpHYIK6UhCqoYqSZrumU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31397@inbox.vuxu.org>

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

New review comment by tibequadorian on void-packages repository

https://github.com/void-linux/void-packages/pull/31397#discussion_r860117004

Comment:
Why? I couldn't find a release tarball where the top directory doesn't match $pkgname-$version

  parent reply	other threads:[~2022-04-27 18:17 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10  9:12 [PR PATCH] " joshuakraemer
2021-06-10  9:30 ` [PR PATCH] [Updated] " joshuakraemer
2021-06-11 22:29 ` joshuakraemer
2021-08-06 19:49 ` joshuakraemer
2021-08-06 20:20 ` joshuakraemer
2021-11-08 18:00 ` mustaqimM
2022-03-30 10:42 ` tibequadorian
2022-03-30 10:46 ` tibequadorian
2022-03-30 18:48 ` [PR PATCH] [Updated] " joshuakraemer
2022-03-30 19:06 ` joshuakraemer
2022-03-30 19:23 ` [PR REVIEW] " tibequadorian
2022-03-30 19:23 ` tibequadorian
2022-03-30 19:25 ` tibequadorian
2022-03-30 20:24 ` tibequadorian
2022-03-31  9:54 ` [PR PATCH] [Updated] " joshuakraemer
2022-03-31 13:36 ` [PR REVIEW] " tibequadorian
2022-04-01 10:01 ` [PR PATCH] [Updated] " joshuakraemer
2022-04-12 15:33 ` joshuakraemer
2022-04-12 15:56 ` joshuakraemer
2022-04-12 19:16 ` joshuakraemer
2022-04-24 17:01 ` mustaqimM
2022-04-24 17:16 ` mustaqimM
2022-04-25  7:48 ` [PR REVIEW] " paper42
2022-04-25  7:48 ` paper42
2022-04-27 17:52 ` [PR PATCH] [Updated] " joshuakraemer
2022-04-27 17:54 ` [PR REVIEW] " joshuakraemer
2022-04-27 17:56 ` joshuakraemer
2022-04-27 18:17 ` tibequadorian [this message]
2022-04-27 18:18 ` tibequadorian
2022-04-27 18:57 ` [PR PATCH] [Updated] " joshuakraemer
2022-04-27 19:03 ` [PR REVIEW] " joshuakraemer
2022-05-24 18:13 ` tibequadorian
2022-05-30 14:18 ` [PR PATCH] [Updated] " joshuakraemer
2022-05-30 14:52 ` joshuakraemer
2022-05-30 14:52 ` joshuakraemer
2022-05-30 14:52 ` joshuakraemer
2022-08-29  2:14 ` github-actions
2022-08-29  5:33 ` mustaqimM
2022-10-16 18:26 ` [PR PATCH] [Updated] " joshuakraemer
2022-10-16 18:51 ` joshuakraemer
2022-10-17 14:41 ` joshuakraemer
2022-10-17 15:30 ` joshuakraemer
2022-10-17 16:02 ` joshuakraemer
2022-10-17 16:15 ` joshuakraemer
2022-10-17 16:19 ` joshuakraemer
2022-10-17 16:57 ` joshuakraemer
2022-10-17 17:42 ` joshuakraemer
2022-10-19 15:49 ` [PR REVIEW] " classabbyamp
2022-10-19 15:49 ` classabbyamp
2022-10-19 15:49 ` classabbyamp
2022-10-19 15:49 ` classabbyamp
2022-10-19 15:49 ` classabbyamp
2022-10-19 15:49 ` classabbyamp
2022-10-20  8:13 ` [PR PATCH] [Updated] " joshuakraemer
2022-10-20  8:27 ` joshuakraemer
2022-10-20  8:32 ` joshuakraemer
2022-10-20  8:41 ` joshuakraemer
2022-10-20  9:27 ` [PR REVIEW] " joshuakraemer
2022-10-20  9:27 ` joshuakraemer
2022-10-20  9:29 ` joshuakraemer
2022-10-20  9:30 ` joshuakraemer
2022-10-20  9:30 ` joshuakraemer
2022-10-20  9:30 ` joshuakraemer
2022-10-20  9:31 ` joshuakraemer
2023-01-19  2:00 ` github-actions
2023-01-22 10:53 ` [PR PATCH] [Updated] " joshuakraemer
2023-02-10 18:47 ` classabbyamp
2023-02-10 18:49 ` classabbyamp
2023-02-10 18:50 ` classabbyamp
2023-03-08 13:14 ` [PR PATCH] [Updated] " joshuakraemer
2023-03-08 13:34 ` joshuakraemer
2023-03-08 15:13 ` joshuakraemer
2023-06-07  2:06 ` github-actions
2023-06-22  1:59 ` [PR PATCH] [Closed]: " github-actions
2023-06-22  3:47 ` [PR PATCH] [Updated] " classabbyamp
2023-06-22  4:04 ` classabbyamp
2023-06-22  4:16 ` classabbyamp
2023-06-22  4:50 ` [PR PATCH] [Updated] " classabbyamp
2023-06-22  5:55 ` [PR PATCH] [Merged]: " classabbyamp
2023-07-16 11:41 ` joshuakraemer

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=20220427181752.3iH4ME2lSp3qZnzhVNHEx9MtpHYIK6UhCqoYqSZrumU@z \
    --to=tibequadorian@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).