Github messages for voidlinux
 help / color / mirror / Atom feed
From: ScrelliCopter <ScrelliCopter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: Qt Phantom Style
Date: Fri, 08 May 2020 09:44:32 +0200	[thread overview]
Message-ID: <20200508074432.9pzlKxPz50yc7t_Tm5rSn0GrpDe9HLy1e5HWhZUxQmY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21371@inbox.vuxu.org>

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

New comment by ScrelliCopter on void-packages repository

https://github.com/void-linux/void-packages/issues/21371#issuecomment-625686693

Comment:
@ericonr That's essentially what I asked for and he said he's not interested in making arbitrary tags for arbitrary milestones that he's not got no intention of supporting, and suggested that if people wanted tagged releases somebody should fork and maintain those tagged releases downstream.

I'm not sure if such practice is frowned upon by the Void maintainers (as a cheap way of getting around the no untagged/no prerelease rules), but if that's okay then somebody could fork and tag a release for inclusion. My template is already ready to go and would require minimal modification to switch from Git to release tarballs.

  parent reply	other threads:[~2020-05-08  7:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27  7:51 [ISSUE] " Val6789
2020-04-27 20:45 ` travankor
2020-04-28  7:59 ` ScrelliCopter
2020-04-28  9:10 ` ScrelliCopter
2020-05-06  4:29 ` ericonr
2020-05-08  7:44 ` ScrelliCopter [this message]
2020-05-08  7:45 ` ScrelliCopter

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=20200508074432.9pzlKxPz50yc7t_Tm5rSn0GrpDe9HLy1e5HWhZUxQmY@z \
    --to=screllicopter@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).