From: faulesocke <faulesocke@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] cutter: update to 2.0.5.
Date: Wed, 02 Mar 2022 13:01:38 +0100 [thread overview]
Message-ID: <20220302120138.BR77JQEy2Zlb1E9nwkwjrbde9PxPIJ9TjHv_ClXYtuw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35901@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 213 bytes --]
New review comment by faulesocke on void-packages repository
https://github.com/void-linux/void-packages/pull/35901#discussion_r817624990
Comment:
The `.so` files definitely DO NOT go into the `-devel` package.
next prev parent reply other threads:[~2022-03-02 12:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 7:53 [PR PATCH] " faulesocke
2022-03-02 8:54 ` [PR PATCH] [Updated] WIP: " faulesocke
2022-03-02 8:55 ` faulesocke
2022-03-02 8:58 ` [PR PATCH] [Updated] " faulesocke
2022-03-02 9:12 ` [PR REVIEW] " paper42
2022-03-02 9:13 ` paper42
2022-03-02 10:26 ` faulesocke
2022-03-02 10:31 ` faulesocke
2022-03-02 10:33 ` faulesocke
2022-03-02 10:38 ` [PR REVIEW] " faulesocke
2022-03-02 11:03 ` paper42
2022-03-02 11:03 ` paper42
2022-03-02 11:03 ` paper42
2022-03-02 11:03 ` paper42
2022-03-02 11:03 ` paper42
2022-03-02 11:03 ` paper42
2022-03-02 11:04 ` paper42
2022-03-02 11:05 ` paper42
2022-03-02 11:06 ` paper42
2022-03-02 11:06 ` paper42
2022-03-02 11:06 ` paper42
2022-03-02 11:47 ` faulesocke
2022-03-02 11:50 ` paper42
2022-03-02 12:00 ` [PR PATCH] [Updated] " faulesocke
2022-03-02 12:01 ` faulesocke [this message]
2022-03-02 12:05 ` [PR REVIEW] " paper42
2022-03-02 12:08 ` [PR PATCH] [Updated] " faulesocke
2022-03-02 12:15 ` faulesocke
2022-03-02 12:25 ` faulesocke
2022-03-02 12:29 ` [PR REVIEW] " faulesocke
2022-03-02 13:08 ` paper42
2022-03-02 13:08 ` paper42
2022-03-04 23:55 ` [PR PATCH] [Merged]: " Johnnynator
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=20220302120138.BR77JQEy2Zlb1E9nwkwjrbde9PxPIJ9TjHv_ClXYtuw@z \
--to=faulesocke@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).