From: rmboggs <rmboggs@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: dotnet-6.0.100
Date: Mon, 28 Nov 2022 20:51:14 +0100 [thread overview]
Message-ID: <20221128195114.uuTot9RCtvq23t14WoAShXaHEhpadnUePG7rR3jaY04@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32974@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
New comment by rmboggs on void-packages repository
https://github.com/void-linux/void-packages/pull/32974#issuecomment-1329669287
Comment:
@ayakael ,
I haven't moved the convo over yet because I still need to do some things first (such as re organizing the package names, testing musl, etc.).
Speaking of which, if I need to add musl specific patches to the packages, what it the best way to do that? Are there flags or special names to use for the patch files? Please let ne know.
next prev parent reply other threads:[~2022-11-28 19:51 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 17:54 [PR PATCH] New package: dotnet-5.0.206.1 TinfoilSubmarine
2021-09-15 18:35 ` rmboggs
2021-09-15 21:48 ` TinfoilSubmarine
2021-09-15 21:50 ` TinfoilSubmarine
2021-09-16 13:20 ` TinfoilSubmarine
2021-09-16 15:51 ` TinfoilSubmarine
2021-09-16 17:53 ` Anachron
2021-09-16 18:04 ` TinfoilSubmarine
2021-09-16 18:45 ` rmboggs
2021-09-16 21:49 ` [PR PATCH] [Updated] " TinfoilSubmarine
2021-09-16 21:51 ` TinfoilSubmarine
2021-09-20 12:18 ` TinfoilSubmarine
2021-09-21 13:25 ` rmboggs
2021-10-09 15:43 ` rmboggs
2021-10-09 15:48 ` TinfoilSubmarine
2021-10-19 14:09 ` TinfoilSubmarine
2021-11-16 3:14 ` jcgruenhage
2022-02-10 4:35 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-02-18 18:15 ` [WIP] New package: dotnet-6.0.100 TinfoilSubmarine
2022-02-18 18:15 ` [PR PATCH] [Closed]: " TinfoilSubmarine
2022-02-19 21:30 ` ayakael
2022-02-27 1:03 ` kawaiiamber
2022-02-27 1:16 ` ayakael
2022-02-27 1:17 ` ayakael
2022-02-27 1:17 ` ayakael
2022-02-27 1:18 ` ayakael
2022-02-27 1:29 ` ayakael
2022-02-27 1:29 ` ayakael
2022-02-27 1:32 ` ayakael
2022-03-01 20:02 ` MichaelSimons
2022-09-27 23:35 ` mjeveritt
2022-09-29 2:54 ` astralchan
2022-09-29 3:05 ` mjeveritt
2022-09-29 3:18 ` ayakael
2022-11-01 23:59 ` rmboggs
2022-11-02 0:31 ` ayakael
2022-11-02 0:45 ` ayakael
2022-11-02 1:14 ` mjeveritt
2022-11-02 1:57 ` ayakael
2022-11-26 17:24 ` rmboggs
2022-11-26 18:29 ` jcgruenhage
2022-11-26 18:59 ` rmboggs
2022-11-26 19:52 ` ayakael
2022-11-26 19:53 ` ayakael
2022-11-26 20:06 ` rmboggs
2022-11-26 20:10 ` ayakael
2022-11-28 17:14 ` ayakael
2022-11-28 18:26 ` JamiKettunen
2022-11-28 19:51 ` rmboggs [this message]
2022-11-28 19:53 ` rmboggs
2022-12-03 19:41 ` rmboggs
2022-12-09 7:30 ` rmboggs
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=20221128195114.uuTot9RCtvq23t14WoAShXaHEhpadnUePG7rR3jaY04@z \
--to=rmboggs@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).