From: kawaiiamber <kawaiiamber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: komorebi-2.1
Date: Thu, 14 Jan 2021 06:25:30 +0100 [thread overview]
Message-ID: <20210114052530.8PWQO4EmE7wA0srbiyQZsHAhSpZ0jk_lrK97b6Ga8HA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27912@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
New comment by kawaiiamber on void-packages repository
https://github.com/void-linux/void-packages/pull/27912#issuecomment-759934556
Comment:
Does void generally allow forks? Also, this app might be considered "complete" in the sense that no more updating is needed to do what it's purpose is. That fork uses `meson`, not gonna lie, I've never heard of meson. I might try patching this template, but this fork idea seems interesting. What do you think? (Thanks for the idea, too :) )
next prev parent reply other threads:[~2021-01-14 5:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 3:57 [PR PATCH] " kawaiiamber
2021-01-14 4:13 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-14 4:49 ` FollieHiyuki
2021-01-14 5:25 ` kawaiiamber [this message]
2021-01-14 5:53 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-14 5:54 ` kawaiiamber
2021-01-14 5:55 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-14 6:06 ` [PR PATCH] [Updated] New package: komorebi-2.2.1 kawaiiamber
2021-01-19 8:52 ` kawaiiamber
2021-03-12 23:09 ` kawaiiamber
2021-03-12 23:10 ` [PR REVIEW] " kawaiiamber
2021-03-12 23:10 ` kawaiiamber
2021-03-12 23:13 ` kawaiiamber
2022-05-02 2:16 ` github-actions
2022-05-17 2:13 ` [PR PATCH] [Closed]: " github-actions
2022-05-17 9:07 ` kawaiiamber
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=20210114052530.8PWQO4EmE7wA0srbiyQZsHAhSpZ0jk_lrK97b6Ga8HA@z \
--to=kawaiiamber@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).